Thus said Richard Hipp on Fri, 27 Mar 2015 05:49:47 -0400: > Indeed. The heuristic used in this case is probably > https://www.fossil-scm.org/fossil/artifact/117b008502a5?ln=1005-1013
Yes, that was it. If I increase this number to 1000000 it handles it just fine (actually it started working around 800000). Should it be possible to influence this particular heuristic with an unexposed setting in the repo? Or a build-time option? Or something else? Or is the number just fine where it is? Maybe the heuristic could dynamically adjust according to other factors (like load average)? Thanks, Andy -- TAI64 timestamp: 4000000055158557 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
