Brian "Krow" Aker (krow) wrote,
Brian "Krow" Aker
krow

Drizzle, boost::unordered_multimap++

=========================================================================================================
REGRESSION REPORT 
=========================================================================================================
MACHINE:  drizzle-build-n01.wc1.dfw1.stabletransit.com
RUN ID:   324
RUN DATE: 2010-07-27T21:48:07.932094
WORKLOAD: innodb_1000K_readonly
SERVER:   drizzled
VERSION:  lp:drizzle/staging
REVISION: 1669
COMMENT:  1669: Brian Aker 2010-07-27 This patch turns the table_cache into boost::unordered_multimap.
=========================================================================================================

TRENDING OVER LAST 5 runs 
Conc   TPS       % Diff from Avg Diff       Norm?          Min        Max        Avg        STD       
=========================================================================================================
16       1993.10          +1.19%      23.37   within norms    1905.44    2010.28    1969.73      26.56
32       2676.28          +1.75%      46.11  outside norms    2568.20    2685.05    2630.17      33.22
64       2622.82          -2.09%     -56.00  outside norms    2613.02    2737.89    2678.82      43.09
128      2621.23          -0.61%     -16.15   within norms    2609.74    2662.30    2637.38      16.41
256      2598.18          +5.50%     135.46  outside norms    2406.50    2599.34    2462.72      68.67
512      2343.83         +52.30%     804.91  outside norms    1318.38    2347.49    1538.92     402.80
1024     1722.08        +104.66%     880.65  outside norms     614.65    1725.52     841.43     440.35


Boost::unordered_multimap versus the hand crafted MySQL HASH?

Boost wins by a long shot. The above is from sysbench. We run it on each and every push that goes into the main tree looking for regression.

Every so often we get to see the opposite happen :)

Thanks to this patch, "Table" now joins the ranks of what we call a "trusted object". This means we can start safely assuming that the destructor on it is working (most of the MySQL codebase was crafted in such a way that you can only use a very limited subset of C++). In all of the new code in Drizzle we can easily make use of C++. There are still a few older bits where we cannot. Having "Table" now work means we can safely work in a number of new areas in the server. One of the biggest changes that will be coming soon is the removal of LOCK_open for a number of new cases.
Subscribe
  • Post a new comment

    Error

    Comments allowed for friends only

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 9 comments