On Thu, Jun 18, 2015 at 1:51 PM, Joerg Sonnenberger <jo...@britannica.bec.de > wrote: > > I'm aware of the sync protocol. My point is that all clusters should > already exist on the public master repository as part of other sync > operations and I would strongly argue that this is the case that should > be optimised for. It is a pity that the nature of the sync protocol > doesn't make it possible to enforce this more strongly.
I assume there was a good reason that the "server" only creates clusters when a client is pulling from it. If the public-facing server is a mirror of a behind-the-scenes master server, that is updated by pulling from the master, then I would expect the public-facing server to not need to create new clusters. Alternately, since clusters are optional, add 2 features to Fossil: (1) an option to suppress automatic cluster creation; (2) a command to perform cluster creation (and possibly other repo optimizations) on demand. That way the repo's write activities could be performed when disk server activities are low.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
