On Tue, Aug 27, 2019 at 5:06 AM Johan Corveleyn <jcor...@gmail.com> wrote:
> On Mon, Aug 26, 2019 at 9:01 PM Mark Phippard <markp...@gmail.com> wrote: > > > > On Mon, Aug 26, 2019 at 1:29 PM Anton Shepelev <anton....@gmail.com> > wrote: > >> > >> I have now set up a post-commit hook that makes an > >> --incremental hotcopy. With the destination on the same > >> machine's HDD, it takes about two seconds, but with a > >> network share it lasts 30 seconds. Is it expected behavior > >> for committing a tiny change in a text file? If not, then > >> where shall I look for the possible performance problems? I > >> have svn 1.8.16. > > > > > > It is probably due to slowness of the IO across network to read what is > in the target repository and then copy over the files. Other than tuning > NFS or whatever you are using there is not much you can do. This is why my > first recommendation was to use svnsync. You could have a second backup > server running and then use svnsync via https or svn protocol to that > server. This basically replays the commit transaction so performs > comparably to the original commit. It also makes it a lot easier to send > the backup around the world or to another data center since it is using a > protocol that is meant for that sort of latency. > > > > Does svnsync also copy locks and hook scripts? > No, neither of those are synced. You would not want the hooks to sync since you need to run different hooks on the backup server but locks are a problem for people using that feature. -- Thanks Mark Phippard http://markphip.blogspot.com/
