On Fri, 2012-09-14 at 23:27 +0200, Borislav Petkov wrote: > (Adding everybody to CC and leaving the below for reference.) > > Guys, > > as Nikolay says below, we have a regression in 3.6 with pgbench's > benchmark in postgresql. > > I was able to reproduce it on another box here and did a bisection run. > It pointed to the commit below. > > And yes, reverting that commit fixes the issue here.
My wild (and only) theory is that this is userspace spinlock related. If so, starting the server and benchmark SCHED_BATCH should not only kill the regression, but likely improve throughput as well. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
