Re: Any data compression between server and client?
Thanks for your reply. My company has developers aboard accessing our SVN server through VPN and they're always complaining that transmissions are very slow. That's why I'm trying to find where the problem is. I was pretty sure there's compression and I'd like to dismiss this as a possible cause. But when I want to confirm it on Tigris foum, I got a rather unfriendly reply: http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061dsMessageId=2616471 Is there any difference between SVN and Subversion, btw? TIA On Fri, Jun 4, 2010 at 21:12, Mark Phippard markp...@gmail.com wrote: Subversion compresses the data it sends over the wire. Using mod_deflate can get you a little extra compression on the entire HTTP request. However, there is a huge memory leak when mod_deflate and Subversion are used together and a client that does not support deflate is used to access the repository. So it is best to stay away from using mod_deflate and the benefits are relatively small since Subversion already uses compression.
Re: Any data compression between server and client?
On Mon, Jun 7, 2010 at 15:02, Hyrum K. Wright hyrum_wri...@mail.utexas.edu wrote: If you are using http or https, there are significant latency issues associated with the Subversion protocol, due in part to the number of roundtrips made to the server for each connection. Subversion 1.7 introduces a new version of the protocol which removes most of the latencies, and should speed things up significantly. OK, waiting impatiently for that version. :) I was pretty sure there's compression and I'd like to dismiss this as a possible cause. But when I want to confirm it on Tigris foum, I got a rather unfriendly reply: http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061dsMessageId=2616471 I think the gist of that message was please let us know where you got such information and please read the documentation before asking questions answered therein. Both are reasonable requests, though could potentially have been framed better. You are must more likely to get assistance if you demonstrate you have done your own research prior to asking questions here. If you read the other replies from that gist (or whatever you call it), he implies that there's no compression in SVN/Subversion. I HAD DONE my research prior to ask the question, but it's impossible to demonstrate that fact. I had searched through a lot of docs. If he could plug into my mind, I could show that moron how much time I had spent on this matter.
Re: Any data compression between server and client?
On Fri, Jun 4, 2010 at 3:08 PM, Je suis la poubelle laps...@gmail.com wrote: I'm looking for some information but can't find it. Precisely, I'm wondering if there's any data compression between SVN server and client. Since SVN is based on web server, and precisely Apache server, and it seems to me that Apache supports gz compressed data through HTTP (if the client supports it as well, of course), so I'm wondering if there's any option to enable this compression. However, I've searched through feature and documentation in official web site but nothing is really found. Could I assume that there's no data compression between server and client? Subversion compresses the data it sends over the wire. Using mod_deflate can get you a little extra compression on the entire HTTP request. However, there is a huge memory leak when mod_deflate and Subversion are used together and a client that does not support deflate is used to access the repository. So it is best to stay away from using mod_deflate and the benefits are relatively small since Subversion already uses compression. -- Thanks Mark Phippard http://markphip.blogspot.com/
