Re: [linux-lvm] Re: [Announce] device-mapper beta3 (fast snapshots)

[Andrew Theurer]

> I don't believe the benchmarks posted at the top of this thread at
> all.  Not only are you claiming poor performance for device-mapper,
> but that this performance degrades as chunk size reduces.
> device-mapper has been tested by a variety of people on many different
> machines/architectures and we've only ever seen a flat performance
> profile as chunk size increases, if anything, there is a very slight
> degradation as chunk size gets too large.

Joe, a couple of things occurred to me.  When you sent out the email about 
device-mapper beta 3 (22/5/2002), and more specifically the user tools 95.07, 
your results http://people.sistina.com/~thornber/snap_performance.html state 
that the default chunk size is 8k.   This is not the case as the code for 
95.07 shows it is 32k:

static int _read_params(struct lvcreate_params *lp, struct cmd_context *cmd,
                        int argc, char **argv)
{
        /*
         * Set the defaults.
         */
        memset(lp, 0, sizeof(*lp));
        lp->chunk_size = 2 * arg_int_value(cmd, chunksize_ARG, 32);
        log_verbose("setting chunksize to %d sectors.", lp->chunk_size);

        if (!_read_name_params(lp, cmd, &argc, &argv) ||
            !_read_size_params(lp, cmd, &argc, &argv) ||
            !_read_stripe_params(lp, cmd, &argc, &argv))
                return 0;

And more importantly, I also could not successfully set the chunksize option 
with "-c" or "--chunksize" on 95.07.  I did not chase down the error, rather 
just changed the default size myself and then ran.  Since you had many people 
test this, is it possible the chunksize did not change at all, and they were 
at 32k all the time?  That would explain why these results are flat, while I 
am getting a wider range.  

Now, this option does work in beta4, so obviously someone working on LVM2 knew 
about it and fixed it.  I am wondering have any of your testers run on beta4?

> For instance I just ran a test on my dev. box, this should
> not be considered a tuned benchmark by any means.
>
> dbench -2 on a 32M RAM system:
>
> no snapshot	8.22
> 8k		13.59
> 16k		13.99
> 32k		13.33
> 64k		12.90
> 128k		13.442
> 256k		13.654
> 512k		13.84

Joe, are you absolutely sure these tests had the disk cache disabled?  That's 
the only hardware thing I can think of that would make a difference.  

It seems we can go 'round and 'round to no end, as long as we have HW 
differences, so I have asked for use on a OSDL system we can both run on. 
This way there is no difference in our HW.  I'll let you know when I hear 
back from them, so we can both test on the same system (if you want to).

-Andrew Theurer