Re: [MMTests] Sysbench read-only on ext3

[Mike Galbraith]

On Tue, 2012-07-24 at 09:19 +0100, Mel Gorman wrote: 
> On Tue, Jul 24, 2012 at 04:29:29AM +0200, Mike Galbraith wrote:
> > On Mon, 2012-07-23 at 22:13 +0100, Mel Gorman wrote:
> > 
> > > The backing database was postgres.
> > 
> > FWIW, that wouldn't have been my choice.  I don't know if it still does,
> > but it used to use userland spinlocks to achieve scalability. 
> 
> The tests used to support mysql but the code bit-rotted and eventually
> got deleted. I'm not going to get into a mysql vs postgres discussion on
> which is better :O
> 
> Were you thinking of mysql or something else as an alternative?
> Completely different test?

Which db is under the hood doesn't matter much, but those spinlocks got
me thinking.

> > Turning
> > your CPUs into space heaters to combat concurrency issues makes a pretty
> > flat graph, but probably doesn't test kernels as well as something that
> > did not do that.
> > 
> 
> I did not check the source, but even if it is true then your comments only
> applies to testing scalability of locking. If someone really cares to check,
> the postgres version was 9.0.4. However, even if they are using user-space
> locking, the test is still useful for looking at the IO performance,
> page reclaim decisions and so on.

I was thinking while you're spinning in userspace, you're not giving the
kernel decisions to make.  But you're right.  If they didn't have
spinning locks, they'd have sleeping locks.  With spinning locks they
can be less smart I suppose.

-Mike


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/