13 replies to this topic

[Serge]

Hello all,

We have imported ufo2000 repository at sourceforge just for testing purposes: http://sourceforge.n...rojects/ufo2000

Currently we have 2 svn repositories:
1. http://lxnt.info:888...pos/ufo2k/trunk
2. https://svn.sourcefo...t/ufo2000/trunk

Please compare these two services and share your impressions here. CVS from sourceforge used have horrible performance, SVN might be slow too, we need to check if its performance is acceptable for us. We need to make a decision whether move to sourceforge or stay on lxnt.info. Until then there will be no commits to either of them.

Moving to sourceforge has the following benefits:
- sourceforge is a available for a long time already and hosts a lot of important projects, so the probability of termination of service is probably lower
- working with sourceforge SVN will improve our sourceforge 'activity rating' and make us easier to get into top sourceforge projects for example we are now in top 10 for 'turn-based strategy' category just because of uploading beta 1007 to sourceforge, using more sourceforge services will improve our 'rating' there.
- somewhat more 'standard' location for repository, so it is easier to find for people who are already familiar with sourceforge CVS/SVN.

Possible drawbacks:
- slow performance

[Kratos]

Well if it serves as a boost in rank, ok. But I can't comment on the speed, I have too fast speed to see much difference. Someone with dial-up please comment.

[Hobbes]

I got broadband as well so I don't see much of a difference. If this move will publicize more the game and attract more developers then I think it is better than to have it on lxnt, although one undesired effect can be that regular Internet users (i.e. people who know the basics about surfing) might feel intimidated by the Sourceforge page.

[Serge]

Well, I'm a dial-up user In reality dial-up users are much less likely to notice any difference as their bandwidth is heavily capped. So no matter how fast or slow is the server, checkout will take approximately the same (long) time as the server can serve data faster than the user can receive them anyway.

[Kratos]

Well that settles it then, moving to sourceforge.

[unclouded]

Sourceforge is actually faster from New Zealand:

$ time svn co http://lxnt.info:888...pos/ufo2k/trunk
real 1m4.504s
user 0m4.494s
sys 0m0.905s

$ time svn co https://svn.sourcefo...t/ufo2000/trunk
real 0m28.181s
user 0m6.490s
sys 0m1.230s

Both were checked out to a RAM drive.

[Serge]

Can you also try some computational intensive svn commands? I tried
# time svn annotate makefile
And got 13 seconds for lxnt.info and 22 seconds for sourceforge. But the numbers can probably vary depending on the load of servers.

And I'll also have a look at making backups of sourceforge repository before making a decision for final switching.

[unclouded]

Can you also try some computational intensive svn commands? I tried
# time svn annotate makefile
And got 13 seconds for lxnt.info and 22 seconds for sourceforge. But the numbers can probably vary depending on the load of servers.

<{POST_SNAPBACK}>

lxnt is faster in this case: 16.452s for lxnt.info and 20.336s for sourceforge

[mindstormmaster]

lxnt.info
checkout trunk - 42.711s
annotate makefile - 1.959s

sourceforge
checkout trunk - 8.445s
annotate makefile - 0.714s

Note: from a datacenter in San Jose, CA, US

[TimberDragon]

I know im only a newbie but ive had some experiance with differant project management systems and in my experiance, sourceforge may have its slow times, but when trouble strikes, they are onto it fairly quickly, but smaller PMS's tend to take longer to fix, as we currently witnessed and i believe its not the first time the system went walk about (MIA) for a while?

I'll go back to my rock now

[Serge]

I know im only a newbie but ive had some experiance with differant project management systems and in my experiance, sourceforge may have its slow times, but when trouble strikes, they are onto it fairly quickly, but smaller PMS's tend to take longer to fix, as we currently witnessed and i believe its not the first time the system went walk about (MIA) for a while?

Yes, that's one of the good reasons to use sourceforge. Is is unlikely for it to get out of service for a long time just because admin is too busy with other issues or is on a vacation

Well, sourceforge only recently started to provide SVN, so we did not have such option before Also as it is a new service, it may still have some issues (or get some issues later as more project start using sourceforge SVN). But anyway, let's try it Also sourceforge SVN is good for us as it provides web interface for SVN commit access management for project admins, so it is easy to add new developers to the project.

[Serge]

OK, the first changes got committed to ufo2000 sourceforge SVN, everyone is encouraged to switch their working copies from lxnt.info to sourceforge (checkout a new working copy from sourceforge and apply the patches you are working on).

Also it is safer to have more people keeping backups of the repository, the instructions are here:
http://sourceforge.net/docs/E09#backup

Also it should be easier for anyone to fork the project any time as getting a full repository is very simple

All the developers are encouraged to register accounts at sourceforge (if they haven't done this earlier) and tell me their sourceforge names.

[Serge]

A mailing list for SVN commit notifications is created: http://lists.sourcef...nfo/ufo2000-svn
Feel free to subscribe, anyway, a changelog is also awailable in the web: http://svn.sourcefor...trunk/?view=log

[Kratos]

Subscribed to mailing list.

Check profile to see my sourceforge name.