[tahoe-dev] Benchmarking

[Kyle Markley]

I'm trying to fix my benchmarking script for the problem of "tahoe start"
not daemonizing on Windows, by having Windows use "tahoe run" instead.  I'm
running into a problem that ought to be basic, but I don't understand it. 
Help!

Command '\Python26\python.exe \Python26\Scripts\tahoe-script.py run
C:\Users\Kyle\AppData\Local\Temp\tahoe.27V5' exited with status 1

Output:
Usage:  tahoe <command> [command options] run [options]
Options:
  -C, --basedir=  which directory to run the node in, CWD by default
      --version
      --help      Display this help and exit.

\Python26\Scripts\tahoe-script.py:  Wrong number of arguments.


Wrong number of arguments?  When I use the exact same command line, but
with "start" instead of "run", the node starts -- no error.  Could someone
explain what's going on here?


I've also run into a usability problem several times.  I've been able to
get into circumstances where my benchmark script exits but the daemon
processes don't.  Then, if I try to create a new node on the same port,
it's not able to bind the web interface to the correct port (because the
old one still owns it).  Instead of getting a helpful error message about
not being able to acquire the port, the node looks like it starts
correctly, but when I try to execute a command on it I get an error that
the node.url file doesn't exist.  Could this condition be cleaned up ...
please?


Finally, I know a lot of work has been going on behind the scenes to
understand the performance regression discovered in 1.8.0.  I hope that
work has been getting people to think about what they'd like to have in an
automated benchmarking environment.  My script (slightly newer version
attached to this e-mail) creates a basic environment for this but it only
knows how to measure the runtime of shell commands.  I suspect we'd like to
be able to get much more detailed timing and network utilization
information.

If someone could describe how that more detailed information is gathered,
I can look into extending the benchmarking script to support it.

-- 
Kyle Markley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tahoe-bench.pl
Type: application/octet-stream
Size: 12230 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100826/c2452f33/attachment-0001.obj>