[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Ways to keep users from checking out too much.

From: Paul Querna <chip_at_force-elite.com>
Date: 2006-02-23 20:00:29 CET

Brian Behlendorf wrote:
> On Wed, 22 Feb 2006, Paul Querna wrote:
>> Brian Behlendorf wrote:
>>> On Wed, 22 Feb 2006, Garrett Rooney wrote:
>>>> It might be possible to do some magic in apache modules to make that
>>>> work, but I'm not sure how off the top of my head. Would certainly be
>>>> nice though.
>>>
>>> mod_throttle? mod_bandwidth?
>>
>> These existing modules wouldn't actually fix much, since they are
>> generally designed to limit the number of concurrent requests, and/or
>> bandwidth used, neither of which is causing the load problem.
>
> Agreed on concurrent requests, but bandwidth used may be relevant, since
> responding to a big request is a combination of server CPU time, local
> disk I/O, and network I/O. If you rate limit network I/O to that
> particular client, then you probably also effectively rate limit the
> other two, since we're not pipelining at all yet, and even when we do
> there'll be a limit to how deep the pipeline will go.
>
>> One thing you can do, is drop the priority of the Subversion HTTPD
>> Process, so it doesn't starve the machine for IO and CPU.
>
> What about a multithreaded httpd? Is there a cross-platform way to drop
> a priority of a thread?

It doesn't work in a multithreaded httpd.

Most people however, better not be running svn in a multithreaded httpd,
if they are using any hook scripts. Its a mess, but thats another whole
topic.

AFAIK, there isn't a cross platform way to drop priority of a thread.

-Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 23 20:01:32 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.