[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] [BUG] Building continuation patch-log is far too slow w
From: |
Mike Hearn |
Subject: |
[Gnu-arch-users] [BUG] Building continuation patch-log is far too slow with large numbers of patches |
Date: |
Sat, 15 May 2004 21:39:03 +0100 |
User-agent: |
Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) |
Hi,
There is a pathologically slow behaviour in arch_prepare_for_tag: it calls
arch_archive_merge_points which in turn calls arch_archive_log for every
possible patch in order to build the list of patches in the continuation
patch log.
This perhaps does not matter for archives with 20-30 patches in. However,
for the WineHQ CVS gateway which currently has about 630 patches with ~100
added per week, this results in 630 apparently non-pipelined HTTP requests
to the remote server simply in order to fill the patch log with what is
IMHO worthless spam.
The solution would seem to be just not adding a list of every patch in the
tag source to the patch log. There's no need for it, and it results in
very slow tagging speed on some archives.
thanks -mike
- [Gnu-arch-users] [BUG] Building continuation patch-log is far too slow with large numbers of patches,
Mike Hearn <=