[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1231098769.5757.43.camel@marge.simson.net>
Date: Sun, 04 Jan 2009 20:52:49 +0100
From: Mike Galbraith <efault@....de>
To: svaidy@...ux.vnet.ibm.com
Cc: Ingo Molnar <mingo@...e.hu>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v7 0/8] Tunable sched_mc_power_savings=n
On Sun, 2009-01-04 at 23:49 +0530, Vaidyanathan Srinivasan wrote:
> I am new to sysbench. I just started few OLTP runs with pgsql. In
> your graph you are plotting and comparing read/write-per-sec and not
> transactions-per-sec. Both the parameter vary in a similar manner.
> Can you please let me know some background on using the
> read/write-per-sec result for comparison.
It means nothing. One result is the same as any other. I prefer low
level read/write but someone else may prefer higher level transactions.
> I assume you have run the above tests on Q6600 box that has single
> quad core package that consist of two dual core CPUs.
Yes. I can go down from there, but not up. Oh darn.
> Can you please
> let me know the sched_domain tree that was build by hacking
> mc_capable(). The effect of sched_mc={1,2} depends on the
> sched groups that was build and their flags.
Hm. I don't know what you're asking. I hacked mc_capable only so I
could have the tweakable handy in case there was something I didn't know
about yet (having _just_ jumped in with both feet;)
> As you have mentioned in your data, sched_mc=2 helps recover some
> performance mainly because of NEWIDLE balance.
Yes, odd.
> You have mentioned clients in the x-axis of the graph, what is their
> relation to the number of threads?
I have 4 cores, and 2 caches. Any relationship is all about cache.
Please feel free to point me to any previous discussion on sysbench
> where the above questions have been discussed.
I haven't seen such.
> Thanks,
> Vaidy
Cheers,
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists