[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: HOWTO: benchmarking monotone (was Re: "memory e
From: |
Nathaniel Smith |
Subject: |
Re: [Monotone-devel] Re: HOWTO: benchmarking monotone (was Re: "memory exhausted" error for 'mtn list status' command) |
Date: |
Thu, 12 Oct 2006 18:49:37 -0700 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Thu, Oct 12, 2006 at 10:05:31PM +0200, Markus Schiltknecht wrote:
> Hi,
>
> Nathaniel Smith wrote:
> >The one in net.venge.monotone.contrib.benchmark. The thread is at:
> >
> > http://thread.gmane.org/gmane.comp.version-control.monotone.devel/7524/focus=7527
>
> I'm currently playing around with that branch. Two things, a minor one:
>
> $ ./drop_caches
> Trying /proc/sys/vm/drop_caches... (requires Linux 2.6.16+)
> $ uname -srmo
> Linux 2.6.19-rc1 i686 GNU/Linux
Oh, the script isn't smart enough to actually _check_ for Linux
2.6.16+, it just spits that warning unconditionally so if it then
fails, you might have a guess why. If you can make the message
clearer, by all means.
Overall the tool is not really polished up for end-users :-).
> And the python traceback below. I didn't look into the source, yet...
*cough* speaking of lack of polish. It might well just be that it's
failing to resolve a path correctly (hence the "No such file or
directory" message in the middle there) or something like that. Path
resolution is a bit hackish all through the benchmark code. OTOH it
could be a bug. Dunno :-). Does it go away if you give a full path
to the mtn executables, though?
-- Nathaniel
--
"But suppose I am not willing to claim that. For in fact pianos
are heavy, and very few persons can carry a piano all by themselves."