Jython, GILs and object locking.

[Carl Banks]

Andrew Dalke wrote:
> Carl Banks:
>> Because, while one processor is doing I/O, the other processor could
>> be preparing the next batch of I/O.  I'd guess Python handles this
>> particular situation OK, since as we all know, the low-level I/O is
>> done without the GIL.
> 
> That sounds like you say something is I/O bound when it is
> preparing data for I/O as well as when doing I/O.   That's different
> than my definition of I/O bound which only includes waiting for
> the system to do I/O, and not waiting for the program to create
> that batch of I/O


Your big computer science words frighten me.

I took it to mean performance was limited by I/O, but I'm sure you
know the nitty-gritty terminology better than I.  I bow to your
superior knowledge.


-- 
CARL BANKS                   http://www.aerojockey.com/software

As the newest Lady Turnpot descended into the kitchen wrapped only in
her celery-green dressing gown, her creamy bosom rising and falling
like a temperamental souffle, her tart mouth pursed in distaste, the
sous-chef whispered to the scullery boy, "I don't know what to make of
her." 
          --Laurel Fortuner, Montendre, France 
            1992 Bulwer-Lytton Fiction Contest Winner