Orbiter-Forum  

Go Back   Orbiter-Forum > Orbiter-Forum.com > Announcements
Register Blogs Orbinauts List Social Groups FAQ Projects Mark Forums Read

Announcements Orbiter-Forum Staff Members will post announcements about the website here.

Reply
 
Thread Tools
Old 11-21-2013, 07:34 PM   #46
kuddel
Donator
Default

Quote:
Originally Posted by Xyon View Post
 I don't think SVN has the same large files capacity.
Subversion per se does not have a filesize limit:
Quote:
A nice feature of Subversion is that by design, there is no limit to the size of files it can handle. Files are sent "streamily" in both directions between Subversion client and server, using a small, constant amount of memory on each side of the network.
Of course, there are a number of practical issues to consider. While there's no need to worry about files in the kilobyte-sized range (e.g. typical source-code files), committing larger files can take a tremendous amount of both time and space (e.g. files that are dozens or hundreds of megabytes large.)
To begin with, remember that your Subversion working copy stores pristine copies of all version-controlled files in the .svn/text-base/ area. This means that your working copy takes up at least twice as much disk space as the original dataset. Beyond that, the Subversion client follows a (currently unadjustable) algorithm for committing files:
  • Copies the file to .svn/tmp/ (can take a while, and temporarily uses extra disk space))
  • Performs a binary diff between the tmpfile and the pristine copy, or between the tmpfile and an empty-file if newly added. (can take a very long time to compute, even though only a small amount of data might ultimately be sent over the network)
  • Sends the diff to the server, then moves the tmpfile into .svn/text-base/
So while there's no theoretical limit to the size of your files, you'll need to be aware that very large files may require quite a bit of patient waiting while your client chugs away. You can rest assured, however, that unlike CVS, your large files won't incapacitate the server or affect other users.
Versioning large files might not be the best idea anyway. Your Apache (or whatever) HTTP Server might need to be configured as well to cope with that long transmissions...In theory it should work, but how reality deals with that might be different
kuddel is offline   Reply With Quote
Old 11-21-2013, 10:01 PM   #47
Face
Beta Tester
 
Face's Avatar

Default

Quote:
Originally Posted by Xyon View Post
 That'd work if it was mercurial...
Well, it is already, so to say. These days conversions between SVN/Git/Mercurial are as cheap as it can get.

But I think I see what you mean, continuing this work-mode with SVN might not make much sense if your SVN-server has to host 100GB of file data for each checkout instead of each clone, regardless of whether or not SVN can actually deal with large file sizes. And of course it would be a single point of failure, as with every centralized versioning system.

Still I'd suggest to not dismiss versioning too quickly, given that decentralized systems exist, and file sharing in this size category today uses even a very similar paradigma (torrenting).
Face is offline   Reply With Quote
Reply

  Orbiter-Forum > Orbiter-Forum.com > Announcements


Thread Tools

Posting Rules
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
Forum Jump


All times are GMT. The time now is 06:34 AM.

Quick Links Need Help?


About Us | Rules & Guidelines | TOS Policy | Privacy Policy

Orbiter-Forum is hosted at Orbithangar.com
Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright 2007 - 2017, Orbiter-Forum.com. All rights reserved.