Sounds like the underlying issue is not the number of requests (or type of request), but the number of SharedMemory instances in use on behalf of request handling at any one time. Maybe put some limits on directly on that. When a request gets to the point where it needs a SharedMemory block it may have to wait if we're at the limit and continue when the water level comes back down under the limit.
And really, it sounds like the limit would want to be applied not just for request handling, but for any uses of SharedMemory blocks in the system. Also, 256 is a pretty low limit. What all do we use SharedMemory blocks for, and is 256 a limit we can live with? --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
