top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

unversioned properties on SVN and size limitations?

0 votes
412 views

Is there a limitation in size on the property value that can be set? Any scalability traps to be aware of (i.e. non-linear increase in time due to increase in size of the property value)? I tried a 4Mb property, seems to work fine...

posted Aug 12, 2014 by Garima Jain

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

One thing to be aware of is that properties were never designed to be large. Property values are always transmitted in full text between client and server (i.e., they're not compressed); they're stored in full text in the repository (not deltified the way file contents are). So the more large properties you have, and the more often you modify them, the less efficient your repository will be, in terms of storage requirements and network bandwidth.

So while you should be able to store a 2 gig property value, I really, really recommend not to do that.

answer Aug 12, 2014 by Naveena Garg
Similar Questions
+2 votes

I noticed that the size of the .svn/pristine directory can get huge over time (several times the expected size). A "svn cleanup" solves the problem, but

  1. this isn't documented (I'm wondering how many users know that);
  2. this isn't automatic.

About (2), svn could warn the user when a cleanup could be needed. I don't know what is the best solution.

+1 vote

When downloading files from the SVN bash (.sh) files are always a little bit bigger than the original committed file.

This seem to only be relevant to bash scripts as far as I can see until now. Ziped files are not affected it seems.

Using notepad++ in windows to compare the files, notepad++ informs that the files are a match. Though doing a MD5sum shows different MD5 hash.

Afraid that it might give effects on finished applications built from the SVN repo, as well as maybe corruption in files.

0 votes

I just moved a subversion repository from an ubuntu linux 12.04 server running subversion 1.6.12 to an ubuntu Linux 14.04.1 server running subversion 1.8.8.

I have been able to export the code to an ubuntu 14.04.1 client running subversion 1.8.8 and when I do a
svn -u status
W155007: ‘home/xxx/src/trunk/c/eco’ is not a working copy

I get this error no matter what directory I do it in and it used to work fine before the move when we were running Ubuntu 12.04 clients with the old repository.

We are using apache2 with ssl for old and new repository.

0 votes

I am looking to integrate SVN support into a Windows application. This application comes as both 32bit and 64bit versions and therefore I would need to have 64bit libraries. I have trouble finding the binaries for Windows 64bit development.

I would not mind compiling one myself, but it seems instructions are sparse and do not directly pertain to 64bit, perhaps because most people are just interested in the clients and 32bit is just fine there for most uses.

Thanks in advance?

0 votes

I received the following message when running SVN UPDATE --SET-DEPTH INFINITY on Windows (build 1.8.9 downloaded from VisualSVN site):

THIS APPLICATION HAS HALTED DUE TO AN UNEXPECTED ERROR. 
A CRASH REPORT AND MINIDUMP FILE WERE SAVED TO DISK, YOU CAN FIND THEM HERE: 
   ....

This seems to happen only when downloading many large files (like third-party DLLs) or many, many small files (I am guessing about 3000 files). This seems to be a problem with 1.8 as 1.7 never did this (again my guess)

I have also tried the svn included with 1.8.7 version of TortoiseSVN and it pops up the "encountered an error and needs to close" message.

Any suggestion on how to solve this?

...