Poor performance of Ruby 1.8.7 when installed with MacPorts

[abc]

Hi,

I've just upgraded to Ruby 1.8.7 using MacPorts (ruby @1.8.7-
p72_1+thread_hooks) and while it runs flawlessly, the performance is
really really poor.

I'm talking in comparison with the Ruby distro that ships with
Leopard, and with my previous installation of 1.8.6 also done with
MacPorts.

For instance a bunch of rspecs i have take 6x to get executed, and ri
takes noticeably more time than previously to load any doc.

Is anyone experiencing the same problem? Do you know how to fix it?

Thanks in advance.

 

[Brian Adkins]

Hi,

I've just upgraded to Ruby 1.8.7 using MacPorts (ruby @1.8.7-
p72_1+thread_hooks) and while it runs flawlessly, the performance is
really really poor.

I'm talking in comparison with the Ruby distro that ships with
Leopard, and with my previous installation of 1.8.6 also done with
MacPorts.

For instance a bunch of rspecs i have take 6x to get executed, and ri
takes noticeably more time than previously to load any doc.

Is anyone experiencing the same problem? Do you know how to fix it?
http://hivelogic.com/articles/2008/02/ruby-rails-leopard


Thanks in advance.

 

[abc]

Fine, thanks for the info.

Do you know what is the exact issue with MacPorts though?

 

[nakatani katsumi]

Hi

I've just upgraded to Ruby 1.8.7 using MacPorts (ruby @1.8.7-
p72_1+thread_hooks) and while it runs flawlessly, the performance is
really really poor.

Is anyone experiencing the same problem? Do you know how to fix it?

The same problem reported at ruby-list-45593.(but Japanese only)

Summary is below.
1. On MacOS X(10.5.5), Ruby1.8.7(p72) compiled with --enable-pthread excute slowly,
as Ruby use time of 70% at rb_call()->getcontext() in fib.rb

2. In MacPorts, ./configure with --enable-pthread option makes config.h using getcontext
like below
#define HAVE_GETCONTEXT 1
#define HAVE_SETCONTEXT 1

3. If you comment out these two lines, you will get normal speed Ruby1.8.7.

4. As Ruby1.9 don't use getcontext()/setcontext(), Ruby1.9 don't care --enable-pthread.

 

[abc]

Thanks for the explanation!

 

[abc]

I filed a bug report and they've just fixed it:

http://trac.macports.org/ticket/17092

 

[Brian Adkins]

I filed a bug report and they've just fixed it:

http://trac.macports.org/ticket/17092

Wow, that was fast. Is the Ruby community great, or what? Thanks
for reporting back with the info.

 

[Nit Khair]

Hi

Could someone explain this to to me. I checked the macports page a few
days back and it said it disables/deletes -enable-pthreads due to some
bug. So does that not mean that it's not there. As pointed above, it
uses thread_hooks instead.

1. Is there any commandline option or other way of my ascertaining
whether my install uses pthreads or not.

Another newb question:

2. One of the prev posts suggests altering config.h and running
/configure. However, if one is using sudo port install how does one do
this? I do not have a "configure" in my ruby folder and my config.h
(/opt/local/var/macports/software/ruby/1.8.7-p22_3+darwin_9_powerpc+thread_hooks/opt/local/lib/ruby/1.8/powerpc-darwin9.4.0/config.h)
does not contain GETCONTEXT.

Thanks.

 

[Roger Pack]

Could someone explain this to to me. I checked the macports page a few

days back and it said it disables/deletes -enable-pthreads due to some
bug. So does that not mean that it's not there. As pointed above, it
uses thread_hooks instead.

apparently somebody said that the most recent macport of it now compiles
with pthreads disabled.

1. Is there any commandline option or other way of my ascertaining
whether my install uses pthreads or not.

from [1]
Maybe try with "ldd" on the ruby binaries--can't remember what the mac
equivalent is but it exists.

Another newb question:

2. One of the prev posts suggests altering config.h and running
./configure. However, if one is using sudo port install how does one do
this? I do not have a "configure" in my ruby folder and my config.h
(/opt/local/var/macports/software/ruby/1.8.7-p22_3+darwin_9_powerpc+thread_hooks/opt/local/lib/ruby/1.8/powerpc-darwin9.4.0/config.h)
does not contain GETCONTEXT.

If you install it from source you should be able to get at it
right...not sure using macports.

GL.
-=R

[1]
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/a31872d447e867cb/40a92a28e9e03793

 

[Luc Heinrich]

If you install it from source you should be able to get at it
right...not sure using macports.

Using MacPorts, you just have to perform the various steps of the
'install' task manually, like this:

% sudo port fetch ruby
% sudo port extract ruby
% sudo port configure ruby

Now go in the work directory and change what you need. You can see
where that directory is by typing:
% port file ruby

After that, you can continue normally:
% sudo port install ruby

 

[Nit Khair]

Using MacPorts, you just have to perform the various steps of the
'install' task manually, like this:

Thanks a lot.

btw, will installing 1.9 from macports create a separate executable such
as ruby1.9 so we can run 8 and 9 in parallel. Or overwrite?


Is there any way via macports to have both running in parallel.
Thanks.

 

[Luc Heinrich]

btw, will installing 1.9 from macports create a separate executable
such
as ruby1.9 so we can run 8 and 9 in parallel. Or overwrite?

The ruby19 Portfile sets the --program-suffix argument of configure to
1.9, so yes you could install Ruby 1.8 and Ruby 1.9 at the same time
on the same machine.

 

[Jason Lai]

Hi Nakatani-san,

That was really helpful information. I digged a bit more based upon
that thread, and for those who compile Ruby 1.8.7 from source on OS X,
here's a more handy way: add 'ac_cv_func_getcontext=no
ac_cv_func_setcontext=no' along with --enable-pthread, e.g.:
../configure --enable-pthread --enable-shared ac_cv_func_getcontext=no
ac_cv_func_setcontext=no

Then the following lines won't appear on your config.h:
#define HAVE_GETCONTEXT 1
#define HAVE_SETCONTEXT 1

Just my 2 cents,
Jason

 

[nakatani katsumi]

Hi Jason

Hi Nakatani-san,

That was really helpful information. I digged a bit more based upon
that thread, and for those who compile Ruby 1.8.7 from source on OS X,
here's a more handy way: add 'ac_cv_func_getcontext=no
ac_cv_func_setcontext=no' along with --enable-pthread, e.g.:

Oh,I missed to follow this problem.
This bug was fixed with 1.8.7-p72_2 of MacPorts, that was reported at
ruby-list:45621(japanese only).
(ruby 1.8.7-p72_1 of MacPorts has bug)
You can use the most up-to-date ruby of MacPorts without any extra option.

 

[Jason Lai]

Hi Nakatani-san,

Thanks for the heads-up. But the issue is still there for those
compiling Ruby 1.8.7-p72 from source right? If so, my little tip may
be of some help.

Cheers,
Jason