./script/about with ruby 1.9.1

Rails
1

Hi In my machine there is Ruby1.8.6 ,1.9.1 and rails 2.3.2 And I created
a new project using Ruby1.9.1 and rails 2.3.2 But when did
./script/about it shows
Ruby version 1.8.6 (i386-linux)
RubyGems version 1.3.1

Why this happens

Thanks in advance
Sijo

2

On Jul 10, 1:25 pm, Sijo Kg [email protected] wrote:

Hi In my machine there is Ruby1.8.6 ,1.9.1 and rails 2.3.2 And I created
a new project using Ruby1.9.1 and rails 2.3.2 But when did
./script/about it shows
Ruby version 1.8.6 (i386-linux)
RubyGems version 1.3.1

Why this happens

If you have multiple versions of ruby installed then how you choose
which one is used may vary. the scripts that come with ruby usually
have
#!/usr/bin/env ruby
which searches $PATH in the usual way. If for example you have ruby
1.9 installed in such a way that ruby19 is the ruby 1.9 interpreter
(and irb19 the 1.9 version of irb etc.) then you need to either change
the shebang line or invoke ruby explicitly (ie ruby19 script/about)

Fred

Fred

3

Hi
Thanks for your it worked Now to test the performance difference
between Ruby1.9.1 and ruby 1.8.6 with rails 2.3.2 what I did is
Created a rails projects using 1.9.1 and 1.8.6 Then created a model and
migrated it to the db using 1.8.6 Ruby+rails Now from the project
created using the 1.9.1 I just make the model only
Now connected this too to the same db For example my model is
School with only one attribute name Then I open console for both the
versions and gave

School.find :all #This has 8 records

And the result I got is

School Load (0.6ms) SELECT * FROM “schools” #from project 1.9.1
School Load (0.6ms) SELECT * FROM “schools” /3from project
1.8.6

 Could you please tell where is the performance difference I cant

understand since it both takes same time How can I measure the actual
performance difference using ruby 1.9.1 with rails 2.3.2 and ruby1.8.6
with rails 2.3.2

Thanks
Sijo

4

Hi, the performance you’ll see is for Ruby code execution. You can
try running the Rails tests or the Ruby spec tests. Also, you can try
using Apache Bench with concurrency greater than 4 targeting pages
which require more Ruby code execution paths.

Good luck,

-Conrad

Sent from my iPhone

On Jul 10, 2009, at 9:04 PM, Sijo Kg <rails-mailing-list@andreas-