Re: performance degradation on kernel upgrade (due to commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f )

[Jeff Moyer]

Jagdish Motwani <jagdish.motwani@xxxxxxxxxxxxx> writes:

> Recently i upgraded my kernel from 2.6.29.6 to 2.6.35.14.
>
> After upgrading i got very poor performance on my postgre database.
[...]
> Using git bisect, i got commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f
>
> Is it a behavior change or am i missing something? Are there any
> workarounds for this?

commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f
Author: Christoph Hellwig <hch@xxxxxx>
Date:   Thu Oct 29 14:14:04 2009 +0100

    blkdev: flush disk cache on ->fsync

This is a data integrity fix, and you really don't want to work around
it.

Cheers,
Jeff
--
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/