Re: GSoC: Add SMT/HT awareness to DragonFlyBSD scheduler

Mihai Carabas <[email protected]>
Newsgroups gmane.os.dragonfly-bsd.kernel
Message-ID <CANg1yUuzjcN1oz+VLc2zOisfmAZpt6GoLihNV32F=STCnVFTiQ@mail.gmail.com>
Hello,

Last week I finished implementing the new heuristic about cache hotness and
obtained some new results in pgbench benchmark:

############enable smt########
kern.usched_bsd4.smt_enable: 0 -> 1
tps = 21651.867019 (including connections establishing)
tps = 21647.787878 (including connections establishing)
tps = 21588.095351 (including connections establishing)
tps = 21607.754026 (including connections establishing)
tps = 21625.132137 (including connections establishing)
tps = 21765.227960 (including connections establishing)
tps = 21646.292802 (including connections establishing)
tps = 21513.203674 (including connections establishing)
tps = 21666.282788 (including connections establishing)
tps = 21656.393030 (including connections establishing)

############disable smt########
kern.usched_bsd4.smt_enable: 1 -> 0
tps = 20843.966453 (including connections establishing)
tps = 20799.100980 (including connections establishing)
tps = 20705.922558 (including connections establishing)
tps = 20834.236784 (including connections establishing)
tps = 20780.154608 (including connections establishing)
tps = 20854.064166 (including connections establishing)
tps = 20768.362228 (including connections establishing)
tps = 20784.986692 (including connections establishing)
tps = 20802.228183 (including connections establishing)
tps = 20823.033787 (including connections establishing)

You can see a difference of ~900-1000tps = 5%.
Note: tps - transactions per second - more is better.
For this test I ran 4 threads for the server and 4 clients. 4 of them are
CPU-intensive and the other 4 are not. The tests were done on my Corei3.
There is no patch commited yet. I will come with another e-mail when is
ready.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.