On Sep 12, 2006, at 2:06 PM, Gary Perez wrote:

>
> On Sep 12, 2006, at 12:35 PM, Chuck Esterbrook wrote:
>
>> On 9/12/06, Gary Perez <[EMAIL PROTECTED]> wrote:
>>
>> Does anyone think this could be Python's GIL kicking in? Perhaps the
>> first thread has acquired the GIL and is not letting it go?
>
> GIL (global interpreter lock) - I'm *very* unqualified to address  
> this.

After a bit of research (http://ldp.paradoxical.co.uk/LDP/LGNET/107/ 
pai.html), I've found:

"In order to support multi threaded Python programs the interpreter  
regularly releases and reacquires the lock, by default every 10  
bytecode instructions. This can however be changed using the  
sys.setcheckinterval() function. The lock is also released and  
reacquired around potentially blocking I/O operations like reading or  
writing a file, so that other threads can run while the thread that  
requests the I/O is waiting for the I/O operation to complete."

And, at first, I thought that the "writing a file" part pertained to  
my situation--which pointed to AppServer's behavior contradicting the  
above statement.

However, the rate-limiting step in the whole thing is the transfer of  
1000s of KB worth of data across the ether. In between the moment  
that the form's submit button is pressed & the actual file write is  
called, that's all upload time - the form hasn't been fully submitted  
until all that goes across the wire, right?

So now, Chuck, I'm thinking it might very well be a GIL problem. To  
get around this, should I explicitly spin off a new thread in the  
status module? I assume I cannot do it on the upload side, since it's  
a standard HTTP POST?

TIA,
-Gary



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to