Use pool allocation for st_table #83
4 participants
gucki
commented
Feb 1, 2012
|
After installing the tuned ruby using https://gist.github.com/1688857 my specs run about 10-20% faster. No problems nor instabilities so far -> +1 :) |
funny-falcon
added
some commits
Feb 9, 2012
burke
commented
Aug 11, 2012
|
Just an added (fairly large number) of datapoint(s): Nearly everyone at @Shopify has been running with this patch in development and production for over half a year with no bugs traced back to it. |
|
Closing this, please refer to feature #5903 on redmine |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage of specialized pool allocation for st_table, st_table_entry and st_table.bins of smallest size.
It gives up to 20% peak performance improvement (assuming C extension like in test below) and up to 4% in average (assuming rails application). Also it gives considerable memory footprint reduction.
Performance testing is here https://gist.github.com/1626602