Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can't comment on the reliability or connection issues that might exist when committing a large file across the network (one referenced post hinted at problems). But here is a little bit of empirical data that you may find useful (or not).</p> <p>I have been doing some tests today studying disk seek times and so had a reasonably good test case readily at hand. I found your question interesting, so I did a quick test with the files I am using/modifying. I created a local Subversion repository and added two binary files to it (sizes shown below) and then committed the files a couple of times after changes were made to them. The smaller binary file (.85 GB) simply had data added to the end of it each time. The larger file (2.2GB) contains data representing b-trees consisting of "random" integer data. The updates to that file between commits involved adding approximately 4000 new random values, so it would have modified nodes spread somewhat evenly throughout the file.</p> <p>Here are the original file sizes along with the size/count of all files in the local subversion repository after the commit:</p> <pre><code>file1 851,271,675 file2 2,205,798,400 1,892,512,437 bytes in 32 files and 32 dirs </code></pre> <p>After the second commit:</p> <pre><code>file1 851,287,155 file2 2,207,569,920 1,894,211,472 bytes in 34 files and 32 dirs </code></pre> <p>After the third commit:</p> <pre><code>file1 851,308,845 file2 2,210,174,976 1,897,510,389 bytes in 36 files and 32 dirs </code></pre> <p>The commits were somewhat lengthy. I didn't pay close attention because I was doing other work, but I think each one took maybe 10 minutes. To check out a specific revision took about 5 minutes. I would not make a recommendation one way or other based on my results. All I can say is that it seemed to work fine and no errors occurred. And the file differencing seemed to work well (for these files). </p>
    singulars
    1. This table or related slice is empty.
    1. POBinary Delta Storage
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USstevek_mcc
    1. USMark Wilkins
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBinary Delta Storage
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, that is about what you would expect from a binary delta so that seems to be working quite well... Hmm. I think I will have to try to do the same test on my own files with a local repo.
      singulars
      1. PO
      1. USColton Phillips
    2. CO@Colton: Out of curiosity, I used 7-Zip (file compression utility) with the default settings and compressed those two files. It resulted in a 1.88 GB file. So the compression used by Subversion in this case seems correct too. They probably both used ZLib.
      singulars
      1. PO
      1. USMark Wilkins
    3. CO@Colton: What DAW software are you using? Not that it really matters, but I'm curious. I use Cakewalk (Sonar) and have thought that I should use some kind of version control with my files but have never actually done it. This little test I did makes me think I may set it up at home.
      singulars
      1. PO
      1. USMark Wilkins
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload