dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

CVSProxy to CVSNT very slow?

( CVSSCC )
Type: Public Status:Closed Created: 01 Apr 04 04:00 Updated: 05 Apr 04 04:00
--> Igor Pushkov (admin)  at 05 Apr 04 04:00 writes

Does this information help you?
--> Igor Pushkov (admin)  at 01 Apr 04 04:00 writes

First of all ensure that you do not have the problem similar to this:
http://www.pushok.com//tickets_messages.php?id=51
Now about CVS and its speed in comparison to SourceSafe. First the
speed is dramatically depends on protocol (access method you use).
1. :local: protocol - file share, similar to SourceSafe
I think that CVS slower there, but not more than 1.5 times than SS.
The main reason, as I think, is that CVS is more comlex (more
functionality). Other reason, that plug-in access CVS as separate
process, wrapping cvs.exe (command line client).
Reason, is that cvs have at least two independent implementations:
windows and linux. This implementation are compatible on command line
level, and wishing to have ability use both implementations we should
work with cvs.exe client. Other reason of this, is that cvs,
especially CVS NT is under active development, and it is too hard to
integrate client code directly.
Please note, that we not recommend to use :local: access mode,
because it is not good for team work (possible errors or other
problems).
2. Simple remote protocols - :pserver: , :sspi:
When CVS NT server and client are on the same PC speed is not
greatly differs with :local: access mode. However, when client and
server are too different PC you will really see some speed reducing.
Lets say that in this case on 100 Mb network all work up to 2 times
slower that with :local: protocol.
Interesting issue that speed not greatly depends on network
bandwidth. Enough to say that no difference between 100 and 10 Mb
network. And even you not have very large binary files, speed will be
similar even on 128k - 256k ASDL or ISDN connections. Think that this
behavior caused by some synchronization issues between client and
server. Also, cvs use data compression in protocol transfers. By
default this compression enabled in plug-in (you can configure it in
options). Switching off compression on fast network you can increase
speed. See the help:
http://www.pushok.com/help/cvsscc/index.php?redirect=ui_config1.htm
Also, what is more important, at least for us. Is that CVS works
much better and faster on low bandwidth connection like general modem.
3. Complex secure protocols, like :ext: (:ssh:)
Such protocols use _complex_ and secure authentication scheme. Each
request to server produces extra traffic for connection establishing.
Speed is about 1.5 times slower than for simple protocols.
And the last, CVS _in general_ slower that SS and may be than other
commercial tools. However, moving from testing of it functionality and
some experiments to real work, you will find (as we do) that this is
_not an issue at all_, especialy taking into account it benefits:
http://www.pushok.com/help/cvsscc/index.php?redirect=basic_whycvs.htm
But in the same time users reports that CVS is much faster than remote
solution for SS (Source Off Site).
And finally, about out plans. Last version of plug-in 1.2 includes
_all_ functionality that we plan to make for such tool. The last issue
that we have is speed, and we are searching ways how to make plug-in
faster. As you may noticed we not limit your right to receive
upgrades, so when new, more faster version will be ready you can
switch to it free.
--> pat (user)  at 01 Apr 04 04:00 writes

I use to use SourceSafe and am now trying your software. I've read a lot
about how sourcesafe was slow. Right now for access over my local network,
CVS Proxy to cvsnt is far slower than sourcesafe ever was. Checking out
files in SourceSafe was almost instant. Over the internet to a remote
server, SourceSafe was really slow, but locally SourceSafe was very fast.
Checking out a whole project through CVSProxy is very slow. Do I have
something setup wrong? Or is this the performance I should expect?
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9545720 visitor since 20 Jan 2003.
891 visitors today and 1 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com