Thus said bch on Mon, 27 Apr 2015 14:27:41 -0700: > 1) On a large repo, this takes an inordinate amount of time. On a sync > (with no updates necessary), the runtime is ~45s (on the first > attempt, I stopped it after ~10 mins of running in order to re-run it > with a time(1) command to collect info) on a network run that took > ~1s.
What is a ``large repo?'' And why would a sync that had no changes even trigger a check for forks? If you are talking about [560483f5], if there was no content synced, then there should be nothing to be checked because g.rcvid should be... 0? (unless perhaps there is a bug). Maybe g.rcvid is being initialized to some strange value that just happens to cause problems. Also, I tested [560483f5] with sync agains every artifact in Fossil and it added no significant overhead, though, perhaps the SQL could be improved, it seemed fine to me. Thanks for the report. Andy -- TAI64 timestamp: 40000000553eb196 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
