On 31/10/2007, Jason Johnson <jason.johnson.081 at gmail.com> wrote:
> 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?
>
All socket/file IO primitives using blocking calls.
To what i see, there is only one set of async primitives -
AsyncFilePlugin. But i'm not sure if it used at first place (i.e.
replaces a FilePlugin).
I think Andreas could answer on this more precisely.

-- 
Best regards,
Igor Stasenko AKA sig.