Berkeley defaults considered dangerous

The defaults in db/DB_CONFIG are still

  set_lk_max_locks 2000
  set_lk_max_lockers 2000
  set_lk_max_objects 2000

Now it happened to me (once again) that I forgot to change the
defaults and filled up the repository with 11700 revisions.
The next checkin failed with

  svn: Berkeley DB error
  svn: Berkeley DB error while reading node revision for filesystem /usr/local/svn/perl/db:
  Cannot allocate memory

I set the three values to 8000 and tried to recover, but got:

  % svnadmin recover perl
  Acquiring exclusive lock on repository db.
  Recovery is running, please stand by...svn: Berkeley DB error
  svn: Input/output error

This seems like a rather serious scalability bug. Shall I file an
issue?

-- 
andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org