Concurrent Futures
Jason Johnson
jason.johnson.081 at gmail.com
Wed Oct 31 06:29:32 UTC 2007
On 10/30/07, Igor Stasenko <siguctua at gmail.com> wrote:
>
> Most of reasons why CPU not utilized at 100% is using a blocking I/O
> calls. Then a simplest solution to not use them and instead of blowing
> up the number of threads use asynchronous I/O . Most major platforms
> support asynchronous I/O and there are many libraries which support
> async data handling almost in each area we need for. We just need to
> build on top of them.
Good point. How many kinds of I/O in Squeak is currently blocking? I
think I heard networking blocks, what about disk?
More information about the Squeak-dev
mailing list
|