Re: Win32 and Win64
From: marc hoffman (mh_at_spam.spam)
Date: 03/05/05
- Next message: marc hoffman: "Re: Win32 and Win64"
- Previous message: Bob Swart: "Re: Dephi 2005 Personal"
- In reply to: Captain Jake: "Re: Win32 and Win64"
- Next in thread: Captain Jake: "Re: Win32 and Win64"
- Reply: Captain Jake: "Re: Win32 and Win64"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 5 Mar 2005 17:45:15 +0100
Captain,
> A perfect example of this is downloading messages from
> newsgroups. Most of the time used in downloading messages from an NNTP
> server
> is spent waiting for the server to respond with the next block of bytes,
> and
> for the TCP/IP stack to retreive them. A single download uses very little
> bandwidth, roughly 30% or so of a 56K connection at any one point in time.
> The CPU usage sits at almost zero the whole time, since downloading uses
> so
> little CPU time. This is a perfect candidate for multi-threading.
Indeed. It's also a perfect candidate for not benefiting from [or needing] a
second CPU (or a virtual second cpu) at all, exactly /because/ that second
thread is blocking most of the time...
The second (real or virtual) cpu doesn't really come into play unless
multiple threads are actually doing enough /real/ work.
- Next message: marc hoffman: "Re: Win32 and Win64"
- Previous message: Bob Swart: "Re: Dephi 2005 Personal"
- In reply to: Captain Jake: "Re: Win32 and Win64"
- Next in thread: Captain Jake: "Re: Win32 and Win64"
- Reply: Captain Jake: "Re: Win32 and Win64"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|