I recently upgraded from a 2.0 GHz Core Duo (without "2") to a 1.83 GHz
i7. The change also involved going from 3GB RAM to 8GB. Effectively a 4
year technology jump. There is a noticeable speed improvement, but
nothing to get excited about.
I have a hunch that an SSD instead of the spindly drive would have been
more effective, and possibly even more cost effective. I'll try this
when they come down in price some more. The reasoning behind my hunch is
that ordinary web apps just aren't CPU-bound and well-behaved
development tools aren't either (so Eclipse/RadRails and NetBeans don't
qualify all of the time).
Both mentioned computers are notebooks (Dell D820 and M6500) running
Debian Linux.
My advice: For your purposes, there probably isn't a noticeable speed
difference between a 2.4GHz dual core and a quad core of the same
generation; 4GB RAM is the minimum; see if you can try out how an SSD
affects speed (and tell us about your experience).
Michael
--
Michael Schuerig
mailto:mic...@schuerig.de
http://www.schuerig.de/michael/
For rails development? Nah, you won't see much of a difference in the
CPUs unless your app do a lot of lengthy pure ruby work with delayed
jobs or something.
Best invesement is in RAM. Lots 'o' RAM so you can keep all your dev
tools and test browsers open at the same time.
-- gw
--
Posted via http://www.ruby-forum.com/.
Buy the best machine you can afford to today, or wait. There will always
be a better deal in a month, it's the nature of the beast. And price vs
performance is always a subjective matter. The i5 will have a longer
useful lifetime, but I don't know how often you change your rig (I run
about a 4 year cycle, and try to buy with that in mind).
During development, 99.999% of the time either machine will be waiting
on you...
I've watched my quad-core Phenom II's work loads (who hasn't popped up
that cpu usage window and left it there for a while?) and it rarely
spikes above 30% in aggregate except when running automated test suites
- at that point, it is satisfying.
Cores/processor speed aside, when I bumped the RAM in my rig from 4Gig
to 8Gig, now that was satisfying. If you can load up the used Thinkpad
with 8 Gig, that might be the winner for me.
Ruby (at least for 1.8) does not use multiple cores. However, the database
server may. And test suites usually hit both.
A talk was given at Lone Star Ruby on how the speaker reduced the run time for
the test suite from 13 minutes to 18 seconds. Part of the changes involved
running pieces of the test suite in parallel on multiple CPUs. I am pretty
sure the talk is on the Web somewhere. Google for "Grease your Suite: Tips
and Tricks for Faster Testing".
HTH,
Jeffrey
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.