[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unconventional Subversion use/scalability

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Sun, 31 May 2009 12:12:14 -0500

Bernhard Glück wrote:
> Hi !
>
> My company is developing a Massivly Multiplayer Online Game. As you
> might know that kind
> of game needs content updates often and reliably. Because of that I had
> the idea to use Subverison
> as our update technology, and i wanted to check if you think that this
> is a viable solution before
> either implementing it or implementing yet another propriatry patching
> techology.
>
> Our Game client at the moment has about 500 MB of "Content" files. Those
> are split up into
> textures ( 10-200 kb files ) models ( 10-5000 kb files ) and audio
> samples ( 10-4000 kb )
> We manage those by having a "Content" subdirectory in our game client
> install directory, where
> they are all placed in a strict hierarchy.
>
> What i wanted to do is setup a master server where on release of a new
> version the release engineers
> will check in the new content files.
> This will then be mirrored to "deployment" repositories which are apache
> servers with their own independent
> Subversion server in the background. ( so we can add new deployment
> servers to improve the number of users
> we can handle )
>
> The game client would integrate a subversion client and on startup do a
> svn update on the content directory from
> one of our deployment repositories.
>
> Do you think this is a feasable solution ?

There are several disadvantages to this scheme including needing more
processing power than necessary on the content servers and having to
store 2 copies of everything on the client, and these don't seem to be
offset by needing to deliver multiple versions concurrently to the
clients. I'd use subversion up to the point of updating the production
copy on a master staging server, then rsync to the delivery servers
(without the svn metadata) and use rsync or some other simple mirroring
technique from the client (rsync needs more server RAM/CPU but might be
worth it if you have large files that have small changes).

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2357301
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-31 19:13:09 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.