Re: [securenfs-devel] Fixed timings in thread-test client

[Nathan Y. <na...@yo...>]

> Yeah, I think the gettimeofday routine is working fine for what
> we want (wall clock time).  I can't imagine how CPU time will be of
> interest to us.

Ditto

> Yes, I believe that 9729 ~ 9.5K.  However, there are 21 clients that
> are sharing the same "pipe" so that is actually 9.5K * 21 bytes/sec, or
> about 200K/sec.  Now, this is assuming that they all start and end at
> the same time which is not exactly true, but hopefully close.  Do you
> agree with that logic?

I agree with the logic, but over a local bus on the same machine we
should see a much bigger pipe that 200k/sec...  Could have something to
do with how we recieve the messages too (byte by byte vs a whole buffer
at a time), but I would think we could get MUCH higher.  Perhaps its
time we ran the server on shemp and beat against it with a few clients
to see what kind of responses we get?

> > I also get different sec/message rates depending on the # of clients.  ~
> > 0.001 with < 10, 0.01 10-15, 0.1 15-20, but that makes sense, as each
> > must share bandwidth with the others.
> > 
> 
> Yes, I get that too, and that makes perfect sense.  The important thing
> is that they share the load equally.  My results show that all timings
> are consistent for all clients (seem to be sharing the load equally).
> Good news!

I agree - Very good news! :-)

Nate