Re: Subverion Performance Tests

Brandon Ehle <azverkan@yahoo.com> writes:

> The results are the averages over 3 runs. The perf test code is
> available at:
>
> http://fishbowl.digitalbytes.net:81/svn/scripts/reposbench.py

It doesn't run :-(

With this change it runs, I don't know if this makes the results
invalid

--- reposbench.py.orig Tue Nov 12 23:52:52 2002
+++ reposbench.py Tue Nov 12 23:51:28 2002
@@ -36,7 +36,7 @@
     err=p.childerr.read()
     if p.poll()<>0:
         print err
- assert(p.poll()==0)
+ #assert(p.poll()==0)
     m=re_collect.search(err)
     assert(m)
     return map(strToSec, m.groups())
@@ -115,7 +115,7 @@
     def __init__(self):
         self.dir=os.path.join(os.getcwd(), 'svnrepo')
         self.wcdir=os.path.join(os.getcwd(), 'svnwc')
- self.url='file://'+os.path.join(os.getcwd(), 'svn')
+ self.url='file://'+os.path.join(os.getcwd(), 'svnrepo')
     def name(self):
         return 'SVN'
     def create(self):

On my system, running the CVS tests produces a low level of disk
activity, much like when I compile, I suspect the CVS filesystem is
cached in RAM and flushed periodically. When running the SVN test
there is intense disk activity, which I suspect is the BDB log files
being written. Does your test simply indicate that the OS native
filesystem is faster that Subversion's BDB filesystem?

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