From: normalperson@...
Date: 2014-05-15T00:08:40+00:00
Subject: [ruby-core:62596] [ruby-trunk - Feature #9841] [Open] [RFC] use ihash for fstring implementation

Issue #9841 has been reported by Eric Wong.

----------------------------------------
Feature #9841: [RFC] use ihash for fstring implementation
https://bugs.ruby-lang.org/issues/9841

* Author: Eric Wong
* Status: Open
* Priority: Low
* Assignee: 
* Category: core
* Target version: current: 2.2.0
----------------------------------------
This results in ~100K[1] memory savings on start up (with RubyGems
loaded) with no user-visible changes.

While this is not the best example of potential ihash-related memory
savings, there is zero-visible impact related to the loss of hash
ordering from this change.

Per-fstring entry overhead is now 24 bytes per-entry on 64-bit,
half of the previous 48 bytes from st_table_entry_t.

[1] as measured by the time(1) command on eglibc 2.13-38+deb7u1
    (Debian 7.0 on x86-64)

Related to Feature #9614

(note: I will have limited Internet access until next week,
 free to take your time in reviewing and responding)

Also viewable via git:
	http://bogomips.org/ruby.git/patch?id=61c27401ed66 (1/2)
	http://bogomips.org/ruby.git/patch?id=67f47a356a7f (2/2)


---Files--------------------------------
ihash-fstring-only.mbox (30 Bytes)


-- 
https://bugs.ruby-lang.org/