[bug-notifications] [ruby18 0004897]: ruby 18 on sparc poorly optimized

Mantis Bug Tracker noreply at opencsw.org
Tue Feb 14 15:58:58 CET 2012


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4897 
====================================================================== 
Reported By:                phil
Assigned To:                bwalton
====================================================================== 
Project:                    ruby18
Issue ID:                   4897
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2012-02-13 20:49 CET
Last Modified:              2012-02-14 15:58 CET
====================================================================== 
Summary:                    ruby 18 on sparc poorly optimized
Description: 
On the same sparc machine, on solaris 10, running the same test
(http://www.thebuzzmedia.com/ruby-19-quick-speed-test/)
takes 3 times as long as a locally compiled ruby.
====================================================================== 

---------------------------------------------------------------------- 
 (0009607) bwalton (administrator) - 2012-02-14 15:58
 https://www.opencsw.org/mantis/view.php?id=4897#c9607 
---------------------------------------------------------------------- 
Are you sure it's loading libruby.so or is it getting libruby18.so?  It
should be linked against libruby18.so and that's what I see on my systems. 
There is a libruby.so, but that was left in place in the event people had
built local gems against it after switching to suffixed file names.  See
CSWlibruby1 vs CSWlibruby18-1.

I still expect to find that the optimization flags are the real slowdown
here, but it's good to know that we're not chasing a different problem.



More information about the bug-notifications mailing list