Linux Desktop Clustering - Pick Your Pricerange 199
crashlight writes: "A Linux cluster on the desktop--Rocket Calc just announced their 8-processor "personal" cluster in a mid-tower-sized box. Starting at $4500, you get 8 Celeron 800MHz processors, each with 256MB RAM and a 100Mbps ethernet connection. The box also has an integrated 100Mbps switch. Plus it's sexy." Perhaps less sexy, but for a lot less money, you can also run a cluster of Linux (virtual) machines on your desktop on middle-of-the-road hardware. See this followup on Grant Gross's recent piece on Virtual Machines over at Newsforge.
Rack Density (Score:2, Interesting)
Re:Is there a real market for this? (Score:2, Interesting)
only 100mbps? (Score:4, Interesting)
Also a bit pricey, but there would be some cost advantage in reduced footprint for some environments.
-Restil
Re:Virtual macines??? (Score:4, Interesting)
Re:Virtual macines??? (Score:3, Interesting)
Many large compute problems are embarassingly parallel, i.e. the same calculation needs to be repeated with slightly different input parameters. There's basically no interprocess communication, just a little forethought about filenaming conventions, total disk and memory usage, etc.
Execution of such tasks reduces essentially to a simple loop:
foreach parameter_set
rsh nodeN myprog outfileM
end
For those programs that actually run a single instance of the code on several CPUs, you have to be acutely aware of how many nodes you use. Your code has its own limits on how well it scales to multiple CPUs, and your cluster imposes limits on how well (in terms of latency and bandwidth) nodes can communicate. Very few codes in this world scale well beyond 64 CPUs, especially not on run-of-the-mill clusters with plain ethernet interconnects. Fortunately, it is trivial to readjust the number of nodes used for each invocation of the code.
Lastly, virtual nodes cannot easily simulate the behavior of real nodes. Again, it's the interconnect latency and bandwidth. When it comes to supercomputing, only trust what you have run and measured on a real life setup with your own code and input data.
Re: - 8 - 800MHz Celerons? (Score:3, Interesting)
*borrowed from Tom's Hardware*
Linux Compiling Test
3.35 minutes for a Athlon XP 2000+
14.2 minutes for a Intel Celeron 800mhz
(now, here's where we stretch it)
Figure 1.7 minutes for a dual Athlon XP 2000+, 50% of the other time.
1.7 x 8 = 13.6 minutes
But, who really compiles with a cluster, really?
It'd still be faster....At least on a few benchmarks, and at least in theory
Re:Linux not ready for the desktop [was Re:Expensi (Score:2, Interesting)
Cost of upgrading what? Did you even read the article? This is a CLUSTER, not your run-of-the-mill desktop or workstation. I could get linux to easily run on an old 486 motherboard that is somewhere in the bottom of my closet.
If any OS is expensive due to upgrades, it is definately Micro$oft OS's. Can you see Windows XP running on a 486 33 mhz? I thought not.
Additionally linux cost a LOT less to administer by IT shops than Microsoft operating systems. With Microsoft operating systems, you have to *click* here, *click* in this text field,etc. I could have ipchains up and running fast than you could have NAT running on Windows2000.
However, this cluster is a great solution to a lot of problems. It would definately free up colocation rack space, and make it easier to do virtual hosting.
r00tdenied
Claims about VMs (Score:2, Interesting)