MARK CALLAGHAN wrote: > I wasn't using pool-of-threads. It took me a while today to figure out > how to use pool-of-threads today. It turns out that the results I > reported were for multi-thread. SHOW VARIABLES doesn't report the > value for scheduler, so I was uncertain about which scheduler was > used.
For the folks who may not have seen the bug report comment, I'm working on a fix for the above... we have an issue with what I_S.PLUGINS is reporting and a lack of a SHOW variable here. Both fixes coming soon. > > Times for pool-of-threads are much worse. I won't report them here as > I don't think this workload is a good fit for pool-of-threads. > >> In addition, you will see serious performance bottlenecks if TCMalloc is >> installed on your benchmark server. MySQL's memory allocation procedures >> simply do not like TCMalloc. > > Or you used a slow & old version of tcmalloc as Domas has suggested on > your blog. > http://jpipes.com/index.php?/archives/296-Drizzle-Performance-Regression-Solved-TCMalloc-vs.-No-TCMalloc.html Yeah - I tried with up-to-date tcmalloc - still no luck. > I did not use tcmalloc in this case. At my previous employer, > performance with tcmalloc was always much better than without. At my > current employer I use a different version of Linux and tcmalloc > doesn't improve things. I have yet to see it make things worse. We're still not sure why, but for Drizzle it _definitely_ makes things worse. Thanks, BTW, for poking at this Mark. More eyes==WIN. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
