Mercurial - High CPU Usage when Pushing Changes to Server Repository?

I really don't see what's wrong with using all the CPU power at disposition to do the job. Using compression probably "helped" because python has to access to wait for the decompression library to do its work.Do you prefer to wait for 5 seconds at 20% load, or 1 second at 100% load?

Normally, I wouldn't care about the CPU cycles either. But this is with one single push. What happens when you have more people using Mercurial and pushing at the same time?

We have about 7 teams that will be using Mercurial once it's fully implemented and we don't know if they will be able to use it if this issue remains. – Athtar Mar 14 at 18:41 pushing locks the repository, so the other user will have to wait until the completion of the operation. – krtek Mar 14 at 18:42 This is not for a single repository though.

Each team has their own repositories that they will be working with. – Athtar Mar 14 at 18:44 Then the CPU is at 100% still, but each job runs a little slower. Still not really seeing the issue unless a push is taking more than a 20 seconds right now, and you think it may reach minutes with multiple users.Is your repo really large?

Was the contents of your changesets quite large as well? If not, then I'm not sure where the problem may have come from. – Mikezx6r Mar 14 at 19:21 A 35 MB push with one to two changesets is taking about 5 minutes right now.

– Athtar Mar 14 at 19:36.

You might be running into issue #135. Try hosting the repository over https instead of accessing it via ssh.

We are using https. – Athtar Mar 14 at 20:27.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.