On Sep 11, 2016 18:18, "Adam Jensen" <han...@riseup.net> wrote: > > On 09/11/2016 05:41 AM, Stephan Beal wrote: > > On Sep 10, 2016 19:31, "Adam Jensen" <han...@riseup.net > > <mailto:han...@riseup.net>> wrote: > >> 1. What is the largest size of any single file that can be checked into > >> a repository? > > > > effectively limited by system memory: fossil needs approx. 2-3x the > > file's size (concurrently in RAM) to create/apply deltas. > > Does it seem reasonable to assume that unversioned files will not have > those (2-3x) memory requirements?
That seems reasonable but i have not yet used that feature nor know the code (whereas i worked with the diff code a couple years ago). > > Also, do you suppose the *initial check-in* [of typical versioned files] > involves that kind of memory usage (2-3x)? Not as i recall, no. Another memory cost comes to mind: the zip command creates zip files in-memory, and may choke on huge repos/files. > > >> 2. How well will the sync command handle large files? > > > > it syncs whole blobs at a time, which are normally (for most versions of > > a file after the first) highly efficient/tiny deltas. > > If a blob is ~1GB, will the data transfer mechanism hang in there and > get the job done? I found this page: > > https://www.fossil-scm.org/fossil/doc/trunk/www/sync.wiki It should always keep going until success or an unrecoverable error. > > which might answer my question after I digest it all (probably requiring > some research (I'm not a Computer Scientist or Software Engineer)). > > But there was something, somewhat unrelated, on that page that did stand > out. It says: > > ''' > 5.4 Unversioned File Sync > > "Unversioned files" are files held in the repository where only the most > recent version of the file is kept rather than the entire change > history. Unversioned files are intended to be used to store ephemeral > content, such as compiled binaries of the most recent release. > ''' > > The phrase "ephemeral content" is a bit disconcerting. It suggests > values and attitudes towards this data which will probably be reflected > in the requirements, specification, and implementation of the software. > > In the use-case I have in mind, this data would be "immutable content" > and should be considered precious. That's not, as i understand it, the intention of unversioned filed. Anything "important" needs to be checked in (versioned). Unversioned files are primarily intended for hosting pre-built binaries and such. ----- stephan (Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
