views:

255

answers:

9

I remember, earlier CPU speed was the most important thing. But today I am confused. Which features determine the most if a laptop can smoothly run Eclipse with lots and lots of projects open?

  • CPU clock speed vs number of cores?
    • What is faster, 4 cores at 1 Ghz or 2 cores at 2,3 Ghz?
    • Which configuration needs more power = less battery life?
  • memory size? Will more than 4GB help a lot?
  • hard disk type -- is a SSD really that much faster? Which type?
  • are there laptops without DVD/CD drive that are still super-fast?
  • I'm looking for laptops with at least 1400 x 1050 pixels
  • Have anti-glare-displays died?
  • Can we get non-extra-wide displays?

Bonus question: What website compares laptops along these features?

+1  A: 

Lots and lots of memory, fast disks. Any modern CPU is going to be good enough for small (100Kloc) projects.

But 7200 RPM disks or SSDs are going to make a bigger difference to system responsiveness, and 8GB of memory should be the starting point if you're even possibly thinking about running test VMs on your laptop for J2EE stacks.

I do well with a Core 2 Duo T2300 (1.6ghz dual core - 3 years old) with 2GB of RAM and a 7200RPM disk, but I'm always bumping into that RAM limit.

  • widescreens aren't going away.
  • anti-glare screens are here to stay - daylight viewable screens are the only other choice, and it's a 1000 premium for those (Dell, Panasonic ToughBook).
Chris Kaminski
A: 
  1. 4 cores at 1Ghz
  2. 4 cores need more power
  3. More memory the better
  4. SSD spanks the average HDD's ass
  5. MacBook Air isn't "super" fast, but it's decent. Why no disc drive?
  6. Several great choices.
  7. Sit in the shade, no glare
  8. Define extra wide?

This isn't your personal shopping advice channel, in general more CPU power and RAM leads to a faster machine.

Josh K
Sitting in the shade doesn't help - you'll just see yourself reflected in the screen as everything around you is lit brighter than the screen itself. It's tolerable, but it's not a solution to daylight viewable. If you need daylight viewable, you have to pay for it (ToughBook, Dell Latitude).
Chris Kaminski
+3  A: 

I would imagine that additional RAM would be the biggest bang for the buck, followed by the SSD. Everything else is a distant third, unless Eclipse can use multiple cores for compiling.

Robert Harvey
And, no matter what computer you get, this is programming you're talking about. It's going to take a few seconds to compile and run, no matter what you're running on - okay, well, unless you're computing on Amazon's Cloud.
rlb.usa
Frankly, I think this advice is simply wrong. Even though Eclipse can be a pig, I have never really seen it RAM starved even on a 2GB system. 4GB should be more than enough unless you are running tons of VMs at once.
Serapth
It hogs most of my 2GB... I think it's odd, I can't explain it. But it does. (Could possibly be due to my plugins.)
aioobe
it's not that the programs (eclipse, JVM, etc) are ram-starved, it's that there isn't enough space left over for the disk cache. That memory isn't usually reported as "used" because it is freed when needed for something else. still, from my obvservations there comes a point where Windows will stop using the free memory for disk cache, unlike Mac and Linux (which will use it all). A SSD would go a long way towards making this moot too.
rmeador
Eclipse can't (yet)
Thorbjørn Ravn Andersen
+4  A: 

Get an i7, and your CPU question becomes basically moot. Otherwise, the answer is basically both, but with Eclipse directly, speed will be more important than cores, but as multiple core will improve overall system performance on a modern OS, its almost a wash.

More than 4GB will make very little difference in 99% of cases. The example of running VM's is one of the few exceptions I can think of.

A SSD as a boot drive will make a pretty impressive difference, that said, outside of boot speed, in day to day development work, it probably isn't worth the cost. Be wary of 5400 RPM or worse, 4200RPM laptops though, as they are common and will kill performance like you wouldn't believe.

As to fast DVD-less machines, sure I suppose so. I don't think I would personally want to go DVD-less these days though.

It should be easy enough getting a machine over 1400x1050 resolution, but screen resolution is definitely where you start to see major price jumps. As to non-wide screen displays, they are getting rarer and rarer, especially at higher resolutions.

As with all performance tuning, its all about removing bottlenecks. A blazing fast CPU that is RAM starved is not going to be blazing fast. A machine loaded with RAM and super fast cores but saddled with a 4200RPM drive is going to spend time waiting on the drive.

Serapth
Best answer on most of the points in my question. Thanks. I still remain undecided of 7200 HDD vs. SDD.
xamde
Must go with the SSD! They make a HUGE difference when developing.
Eric P
If money is no issue, definitely go with a SSD for your system partition and ideally a 512/1TB second drive. Its always good to keep your data on a physically separate device than your system anyways, makes reinstalls a breeze. If you are budget minded, I would recommend checking out a Dell Studio 17 with an i7 proc. Of all the pieces in the puzzle though, make sure you get an i7! Easily best bang for the buck part of your purchase.
Serapth
A: 

Go for 7200 RPM hardisk.That will help you to load the files in the project faster when its a lot in number.

Shyju
Uh? Faster than a SSD drive?
xamde
A: 

That's simple. You start with a 17" MacBook Pro with a i7, 8GB and a 512 GB SSD and a non-glare display for $4249 list. Then you decide what you do not need...

Stephan Eggermont
A: 

As much memory as you can possibly afford. What Eclipse doesn't use on its own, the operating system will use as a disk buffer.

The rest of the computer is much less important.

Thorbjørn Ravn Andersen
+1  A: 

I would say:

1) RAM. RAM. RAM. RAM.

2) Related to RAM: If you use Eclipse, make sure you are letting it use enough heap space with -xmx in eclipse.ini. For some reason, the defaults in Eclipse are rarely increased, so you could have the top machine and still be gimping it. You might see a difference even with your current machine

3) Disk speed. When RAM cuts out (and when there's compilation). Go for speed, not size. You won't be storing much on your HD anyway and cheap externals are super cheap now.

4) Extra cores on the CPU

5) A nice widescreen monitor to use when you're on a desk. Seriously, you only got one neck and one pir of eyes. Save em.

Uri
A: 

CPU and Ram will both work together to create a faster environment.

Forgoten Dynasty