diff options
author | Sean Griffin <sean@seantheprogrammer.com> | 2018-03-14 13:42:40 -0600 |
---|---|---|
committer | Sean Griffin <sean@seantheprogrammer.com> | 2018-03-14 13:42:40 -0600 |
commit | 066919f245e181dd2a9986343e3fabb3c4485fef (patch) | |
tree | c207aae01b3ff5cf82129193f93e58682e3a558a /railties/.gitignore | |
parent | b3b193f7d65357970e72711d42db8070dcf92ce4 (diff) | |
download | rails-066919f245e181dd2a9986343e3fabb3c4485fef.tar.gz rails-066919f245e181dd2a9986343e3fabb3c4485fef.tar.bz2 rails-066919f245e181dd2a9986343e3fabb3c4485fef.zip |
Don't marshal ActiveSupport::Cache::Entry objects twice
When upgrading to Rails 5.2 we're seeing
`ActiveSupport::Cache::Entry#compress` and
`ActiveSupport::Cache::Entry#should_compress?` as the highest usage of
our CPU. At least some part of this is coming from the fact that objects
are being marshaled multiple times. This memoizes the marshaled value to
eliminate half the problem.
Diffstat (limited to 'railties/.gitignore')
0 files changed, 0 insertions, 0 deletions