RE: 1+ hours to merge, can you beat that?

Thanks, but I doubt IPv6/IPv4 is the problem here. All other operations work just fine. Does it matter?

It looks like I am going to give all developers access via remote desktop to the server so they can have their working copy on the server and merge there. Virtualization, that's the way to work in the 21st century.

Cheers,
Roman

-----Original Message-----
From: Ivan Zhakov [mailto:ivan_at_visualsvn.com]
Sent: Sunday, October 11, 2009 1:05 AM
To: Roman Korchagin
Cc: users_at_subversion.tigris.org
Subject: Re: 1+ hours to merge, can you beat that?

On Sat, Oct 10, 2009 at 3:47 PM, Roman Korchagin
<roman.korchagin_at_aspose.com> wrote:
> Thanks to your replies. To summarize, so far I see two suggestions, but
> unfortunately none apply here.
>
>
>
> 1.������ Slow because it is an i/o intensive task.
>
> I can tell that the client i/o is definitely not stressed. The antivirus is
> off. The disk is idling basically. Performance monitor shows nothing worth a
> notice. The server is idling too.
>
>
>
> 2.������ Lots of nodes svn:mergeinfo will slow things down.
>
> We only have svn:mergeinfo at the branch root and in this test we merge from
> the trunk head to the branch head and the difference is not big.
>
3. Client using IPv6 while server listens only on IPv4 interface.

-- 
Ivan Zhakov
VisualSVN Team
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2405852
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].