Well, it depends how you view the original question.
Sure, you could eventually find some purpose to the 48 cores, but that implies an active search for such a purpose and basically a side-project. I dunno, I might just collocate the server and sub-rent virtual machines or do some shared hosting -- but that's not what I care about.
So -- for my current tools and work-flow, 48 cores isn't needed. Pretty sure some scientist or video editor might replace his cluster with this thing but as a normal user and developer I would severely under-utilize the hardware.
Comments
I would have them sit idle most of the time, since most of my tasks are usually IO bound.
Add them to a grid, so others can use them when you don't need them? Seti@home, but where you get paid for your cycles?
Well, it depends how you view the original question.
Sure, you could eventually find some purpose to the 48 cores, but that implies an active search for such a purpose and basically a side-project. I dunno, I might just collocate the server and sub-rent virtual machines or do some shared hosting -- but that's not what I care about.
So -- for my current tools and work-flow, 48 cores isn't needed. Pretty sure some scientist or video editor might replace his cluster with this thing but as a normal user and developer I would severely under-utilize the hardware.