| commit | 979ebcf91705709be5041a3be4514e5f1f6ec02c | |
| author | Eric Wong <e@80x24.org> | |
| Tue, 28 Feb 2017 23:58:15 +0000 (28 23:58 +0000) | ||
| committer | Eric Wong <e@80x24.org> | |
| Wed, 8 Mar 2017 09:18:26 +0000 (8 09:18 +0000) | ||
| tree | 5e339d5cbf681872ed1ef83ddb9b9b2cc3598b21 | treesnapshot (tar.gz zip) |
| parent | ff13ad38ba9f83e0dd298be451aac7c75145d33b | commitdiff |
unicorn_http: reduce rb_global_variable calls
rb_global_variable registers the address of the variable which
refers to the object, instead of the object itself. This adds
extra overhead to each global variable for our case, where the
variable is frozen and never changed.
Given there are currently 59 elements in this array, this saves
58 singly-linked list entries and associated malloc calls and
associated overhead in the current mainline Ruby 2.x
implementation. On 64-bit GNU libc malloc, this is already
16 * 58 = 928 bytes; more than the extra object slot and array
slack space used by the new mark array.
Mainline Ruby 1.9+ currently has a rb_gc_register_mark_object
public function which would suite our needs, too, but it is
currently undocumented, and may not be available in the future.
rb_global_variable registers the address of the variable which
refers to the object, instead of the object itself. This adds
extra overhead to each global variable for our case, where the
variable is frozen and never changed.
Given there are currently 59 elements in this array, this saves
58 singly-linked list entries and associated malloc calls and
associated overhead in the current mainline Ruby 2.x
implementation. On 64-bit GNU libc malloc, this is already
16 * 58 = 928 bytes; more than the extra object slot and array
slack space used by the new mark array.
Mainline Ruby 1.9+ currently has a rb_gc_register_mark_object
public function which would suite our needs, too, but it is
currently undocumented, and may not be available in the future.