On 24 Oct 2000, Ben Collins-Sussman wrote:
> For some reason, apr's pserver is *super* slow. When you update
> inside apr/, it often takes a minute or more before anything prints to
> stdout. Just be patient -- once it finally starts the update, it
> clips along.
I've noticed this happens too - and fwiw, I am responnsible for the
admin of apache.org, so I've got an interest in fixing this. =)
Given that we have a few people here who are familiar with CVS internals,
let me ask - before a cvs update starts updating the remote client, there
is always this delay. What's it doing? Is it recursing through the
client and server trees, noting where the deltas are first, before sending
any data? It appears to be building a huge dir in /tmp for the
specific process, building up the actual content to be shipped; I presume
this means recursing through the whole tree, which for something like apr
can be kinda big (and locus's I/O is pretty impacted). Karl/Jim, does
this make sense? If so, is there a way to have that streamed, so that
network I/O doesn't have to wait for all that disk I/O to complete first?
Brian
Received on Sat Oct 21 14:36:12 2006