Am Freitag, 26. Januar 2007 01:11 schrieb Gunter Ohrner: > waa__read_or_build_tree[waa.c:1714] read tree = 0 > waa__partial_update[waa.c:1981] update 0=dirA/dirB (...) > waa__update_tree[waa.c:1593] doing update for . ... 1 left in 0x80653ac
> After that it starts to scan all entries in the repository, not just > the entries below. Ok, this statement is correct, but that's not the part which slows fsvs down. Actually the update_tree finishes pretty quickly. The slow part happens on commit: Probably to query the repository for file changes, fsvs does ci__directory[commit.c:291] ./dir/file: action is 200, type is 1 for each managed file, which takes 200 ms - 500 ms for a server roundtrip (or several roundtrips, I'm not sure). With 70000 managed files, that takes more than 5 hours, even if no single file has changed... So, in combination with the after-sync-repos-partial-ci-bug, this was the reason for my extremely long-running partial commit. Did fsvs < 1.0.15 also do this on every commit? Wouldn't it be possible to query the server for file / attribute changes between the current local and svn HEAD revisions (as "svn diff --summarize" does) and just to ask the server for files reported as added, removed, modified or replaced? Greetings, Gunter -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ "Of course, just because we've heard a spine-chilling, blood-curdling scream of the sort to make your very marrow freeze in your bones doesn't automatically mean there's anything wrong." -- (Terry Pratchett, Soul Music) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
pgpONVdAWWYGM.pgp
Description: PGP signature
