RE: What is recommended process for large binary files?
"Matthew Sheats" <[email protected]> Thu, 22 Apr 2004 14:05:23 -0600
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
=20 We routinely store 50 to 80 MB files in Vault (installers, Power Point presentations, etc) without issue. Heck our entire distribution CD comes straight out of vault as one "Get Latest Version". It works great for this stuff. The only catch is the weekly backup of the 12GB (and growing) SQL database but even that is no problem. Matt Sheats HYTEC, Inc. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dan Schreiber Sent: Thursday, April 22, 2004 1:56 PM To: Clayton Dool; Vault-List (E-mail) Subject: RE: [vault-list] What is recommended process for large binary files? Vault should be able to handle 20MB binary files without much problem. They will of course take longer to compute deltas on, and longer to retrieve. The only issues I can think of would be: 1. If you use MSDE instead of SQL, you'll run up against the 2GB limit faster this way. 2. Both the client and server RAM usage will go up as you handle large files. IIS seems to like to grab RAM for an entire file it is uploading or downloading. A 20MB file shouldn't be a problem for this, but thought it should be mentioned. Of course, once you do the Get the first time, the rest of the Gets are deltas, so it won't be transfering nearly as much data. Also, on the client, it does store a baseline version, so you'll be storing 2 copies of the file. -Dan > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of Clayton=20 > Dool > Sent: Thursday, April 22, 2004 1:48 PM > To: Vault-List (E-mail) > Subject: [vault-list] What is recommended process for large binary=20 > files? > > > We have several large binary files (20 mb each) that we currently have > in vault. These are data files that are released with our product. =20 > What is the recommended process for dealing with large files? Keep=20 > them in vault, checking in changes as minimal as possible between releases (branching)? > Keep them separate in a folder and manually mark them per release? > > > --------------------------- > Clayton Dool > Application Developer, Axium > 503.350.2156 > [email protected] > > > _______________________________________________ > vault-list mailing list > [email protected] > http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list _______________________________________________ vault-list mailing list [email protected] http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list