2009/4/18 Aaron Watters <aaron.watt...@gmail.com>:
>
>
>
> On Apr 17, 7:41 am, Graham Dumpleton <graham.dumple...@gmail.com>
> wrote:
>> 2009/4/17 Andy <selforgani...@gmail.com>:
>>
>> That said, the GIL is not as big a deal as some people make out...
>
> Yes, I'd suspect that in almost all real cases
> the bottleneck will be disk I/O and database
> access (which are also unaffected by the GIL).
> These things are awfully tricky to philosophize
> about from first principles -- you need to find
> a slow application and run "top" etc to find out
> what the real problem is.  I'd even go so far as
> to guess that the hypothesis about mod-python
> may have been based on guesswork.

Which hypothesis about mod_python? The one I blogged about in:

  http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html

If that is what you mean then yes, I haven't experienced it first
hand, but logically knowing how Apache works and applying common sense
about characteristics of fat Python applications, it is a good as
hypothesis as any at the moment. :-)

Graham

>   -- Aaron Watters
>      http://aaron.oirt.rutgers.edu/myapp/docs/W1500.whyIsWhiffCool
>
> ===
> She was dirty, flirty, musta been about thirty
>   -- Stones, 60's
> She was shifty, nifty, musta been about fifty
>   -- Stones, 80's
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to modwsgi@googlegroups.com
To unsubscribe from this group, send email to 
modwsgi+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to