Issue #3924 has been updated by Masaya Tarui.



Hello,

Require performance has been imporved a little at r31875, i think.
Please compare the proposal with it.

Thank you.



Yusuke wrote:
> 2011/5/31 Xavier Shay :
> > 1.8 actually does exhibit the same performance curve, just over a greater
> > value of N. See this graph (x-axis doubled from other benchmarks) 
> Hmm... Okay.  However, it is hard to fix this issue in 1.9.x,
> I think.
> To be honestly, $LOADED_FEATURES as an array is uncool, or even
> considered as a "specification bug", though.

I agree with you.


----------------------------------------
Bug #3924: Performance bug (in require?)
http://redmine.ruby-lang.org/issues/3924

Author: Carsten Bormann
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 1.9.3
ruby -v: -


=begin
 Running irb < /dev/null in 1.9.2 causes 3016 calls to lstat64.
 
 For instance, there is a sequence of 28 repetitions each of lstat calls to all 6 non-empty path prefixes of /opt/local/lib/ruby1.9/1.9.1/irb.rb -- a total of 170 lstats apparently just to load this file; another set of lstats then occurs later for another 18 (times 6) times.  Clearly, something is running amok in the calling sequence rb_require_safe -> realpath_rec -> lstat.
 
 Another example: Running a simple test with the baretest gem causes 17008 calls to lstat.  According to perftools.rb, 80 % of the 1.2 seconds of CPU is used in Kernel#gem_original_require (and another 12 in GC, some of which may be caused by this).
=end



-- 
http://redmine.ruby-lang.org