diff options
| author | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-11-27 14:42:30 +0900 |
|---|---|---|
| committer | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-11-27 21:38:07 +0900 |
| commit | 6f27fa4f7d52bfaea4fd1bd7605bda28e302e74c (patch) | |
| tree | bbe0c2cd3e9eb33bf0c38e6d6d185dc1f916441c /test | |
| parent | 177bc652a8110c1350c0e6df8cb17158e44e18dd (diff) | |
prefer class_serial over m_tbl
Decades ago, among all the data that a class has, its method
table was no doubt the most frequently accessed data. Previous
data structures were based on that assumption.
Today that is no longer true. The most frequently accessed field
moved to class_serial. That field is not always as wide as VALUE
but if it is, let us swap m_tbl and class_serial.
Calculating -------------------------------------
ours trunk
Optcarrot Lan_Master.nes 47.363 46.630 fps
Comparison:
Optcarrot Lan_Master.nes
ours: 47.4 fps
trunk: 46.6 fps - 1.02x slower
Notes
Notes:
Merged: https://github.com/ruby/ruby/pull/2701
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions