| 1 |
On Sat, Jan 19, 2008 at 01:01:04AM +0200, Alon Bar-Lev wrote: |
| 2 |
> On 1/19/08, Robin H. Johnson <robbat2@g.o> wrote: |
| 3 |
> > My core concern with the SVN http://, was the crappy performance it |
| 4 |
> > provided compared to svn://. The main rsync tree has never been |
| 5 |
> > available for iterative syncing via http://, just had tarball snapshots |
| 6 |
> > and deltas instead. |
| 7 |
> If I understand correctly, the performance of svn under apache is |
| 8 |
> better than the svnserver, the same for git... Well... This is only |
| 9 |
> for my experience. |
| 10 |
> In git case, apache is used to transfer files, and it is much better |
| 11 |
> in this than the most available alternatives. |
| 12 |
Umm, I think you've got things a bit reversed here. |
| 13 |
The core problem with using both SVN and Git over HTTP, is the number of |
| 14 |
round trips required. Git provides the best example, if the server side |
| 15 |
isn't already packed, each object needs to get fetched individually. |
| 16 |
Whereas the git:// protocol effectively sends 'I have rev XYZ, give me |
| 17 |
everything up to HEAD.' One message in each direction, with a slight |
| 18 |
wait in the middle while the server prepares the response. |
| 19 |
|
| 20 |
> In svn case, apache provides the concurrency missing from svnserve. |
| 21 |
svnserve running under xinetd so it's niced and set to a max of 10 |
| 22 |
concurrent users. I benched it up with 30 concurrent updates myself, but |
| 23 |
I want to save room for now. |
| 24 |
|
| 25 |
> Even if tree signing will be available, the developers should work in |
| 26 |
> secured channel... ssh or https... The users will benefit from the |
| 27 |
> signing and not require secured channel. |
| 28 |
> |
| 29 |
> Until signing will be available, I think it is very important for us |
| 30 |
> to provide reliable source. |
| 31 |
The git:// and svn:// are for the anonymous side - I did state |
| 32 |
that clearly in my original post. Git commits are using git+ssh:// (via |
| 33 |
gitosis), and while I'd like to do the same for SVN, it will probably |
| 34 |
remain SVN-over-https:// for now. |
| 35 |
|
| 36 |
-- |
| 37 |
Robin Hugh Johnson |
| 38 |
Gentoo Linux Developer & Infra Guy |
| 39 |
E-Mail : robbat2@g.o |
| 40 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives