3 ms·
This is a political issue as the article already indicates: even though you could just buy very energy efficient, but worse performing ARM based servers with (d
by tluyben2 14y ago
This is a political issue as the article already indicates: even though you could just buy very energy efficient, but worse performing ARM based servers with (depending on your needs) networking/memory/IO focus, it is easier to do the 'no-one has been fired for buying IBM' route: if something goes wrong, it's easier to say that you bought the fastest thing money can buy (who cares if it's running at 6% CPU util) than going the 'experimental' route with low energy equipment in servers risking downtime which could be because of your decision.
The problem is of course that if you go below the enterprises, it's probably even worse, where high powered servers with cpanel running max 400 accounts per server could be put on a microcontroller costing a few cents on average. I ran servers which had 300-400 accounts on them and where the TOTAL number of sites had a few 100 requests per month. I think this is the case for most of the 100s of 1000s of servers running at hostgator, godaddy etc. The whole problem is 'peaks'. Management will ask you 'nice story, but what about peaks'? So you just buy the fastest thing there is, slap VMWare on and hope for the best. I think power management like in mobile phones would not be that bad for this purpose; most of the time you just switch off all cores but one and power down the clockspeed; when a peak comes, you just power up fully.
- travem 14y agoIn the enterprise datacenter level it is not uncommon for sysadmins to use VMware's Distributed Resources Scheduler (DRS) coupled with Distributed Power Management (DPM) to balance workloads and power down underutilized hosts. There are probably similar solutions from other vendors (disclosure: VMware employee)