Re: ra_serf in Windows binaries

On Fri, Aug 1, 2008 at 7:36 AM, Kenneth Porter <shiva_at_sewingwitch.com> wrote:
> --On Thursday, July 31, 2008 4:36 PM -0700 Justin Erenkrantz
> <justin_at_erenkrantz.com> wrote:
>
>> Besides pipelining, ra_serf uses multiple HTTP connections for update
>> which can help dramatically in some cases. (Especially when the other
>> server is beefy enough to truly handle concurrent requests.)
>
> Is it sufficient for the client and server to be multi-core, or does this
> require the different requests to hit different proxies?

I'd say it is probably more about how well the server can saturate the
network available to it. Consider that virtually all web browsers use
both of these techniques too. So it is nothing new for Apache in
general to handle.

> What actually takes most of the time during a checkout or a commit? Those
> are the operations that feel slow.

Checkout is the slowest operation. The working copy adds a lot of
overhead to that operation. I find commit in general to be quite
fast. Crawling a large working copy can be slow. Committing certain
types of large binaries can be slower than it needs to be.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org