[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit with huge log message

From: Paul Burba <ptburba_at_gmail.com>
Date: Tue, 11 Aug 2009 09:55:25 -0400

On Tue, Aug 11, 2009 at 5:55 AM, Senthil Kumaran S<senthil_at_collab.net> wrote:
> Senthil Kumaran S wrote:
>> Also, the above shows that there is a limit for the size of log message, do
>> anyone know what is the maximum size of log message that can be committed. If
> Further look at this revealed that, this is not a limitation with subversion
> per se, it is a limitation with apache (may be not a limitation but for good?)

Hi Senthil,

Regardless of the Apache limitations, there are some effective
limitations to svn:log (or any other property) sizes in Subversion's
basic design. As "The Subversion Book" notes:

"While Subversion places few restrictions on the names and values you
use for properties, it has not been designed to optimally carry large
property values or large sets of properties on a given file or
directory. Subversion commonly holds all the property names and values
associated with a single item in memory at the same time, which can
cause detrimental performance or failed operations when extremely
large property sets are used."

Log messages get passed around as char * | svn_string_t * |
svn_stringbuf_t * and stored in hashes and arrays as such.
Unfortunately the memory management around these allocations is pretty
"loose" and we seem to copy the log message into a long lived pool
every chance we get :-( I made a slight improvement in r37868, but I
suspect further improvements are going to be a lot more work.


Received on 2009-08-11 15:55:51 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.