I got an excellent response on libMicro running on Mac OS X from the
darwin-kernel list at lists.apple.com, and in the spirit of open
communication I thought I'd share them here (he asked to be anonymous).
Firstly, a little more background on my efforts to get the full suite
to run on OS X.
[resend, fixing attachment]
Ok. Attached is a preliminary DEBUG vs. non-DEBUG comparison; I
eliminated the one test which was very obviously misfiring. It could be
that there are others which are also misbehaving.
For those not acquainted with what I'm measuring: there are two ways to
build th
Dan Price wrote:
On Thu 18 Aug 2005 at 01:54AM, Phil Harman wrote:
Dan,
This is related to the undersized batch issue I mentioned in an earlier
thread. From your data we can see that the batch (sample) size is 1.
This is broken. It means that alternate batches will use PROT_NONE and
PROT_
On Thu 18 Aug 2005 at 01:54AM, Phil Harman wrote:
> Dan,
>
> This is related to the undersized batch issue I mentioned in an earlier
> thread. From your data we can see that the batch (sample) size is 1.
> This is broken. It means that alternate batches will use PROT_NONE and
> PROT_READ | PROT
Dan,
This is related to the undersized batch issue I mentioned in an earlier
thread. From your data we can see that the batch (sample) size is 1.
This is broken. It means that alternate batches will use PROT_NONE and
PROT_READ | PROT_WRITE. I suspect one of these is cheap, and the other
is no
I'm seeing the following libmicro computation regarding mprotect, which
looks fishy to me. Interesting to note that libmicro eventually
discards all of the results > 100 usecs, leading it to conclude that
this system call is taking 1usec per call. Plus, there's a very odd
distribution of times.
Hi Kevin,
This workload is running out of files to create after 25 seconds, with the
default set of 1000 files.
The creation phase is pre-defining a fileset of 1000 filenames (without
actually creating them), then creating them during the run. So, for a longer
run more filenames will be requir
Richard:
Thanks for creating this workload. I am having some problems with it, though.
When running filebench directly (not from runbench), it complains that there is
a syntax error and it is expecting a token.
filebench> load kevin
4297: 2.479: syntax error, token expected on line 32
The