> From: Luke S Crawford [mailto:[email protected]]
> 
> http://www.supermicro.com/Aplus/system/1U/1042/AS-1042G-TF.cfm

Incidentally, Luke (or anyone else) ... Do you own any of these systems?  I
guess I don't care if it's Supermicro, or any other brand.  But the
supermicro link is here.

As long as it's AMD processors.

Would you be willing to actually measure the power draw of these systems?
I'll happily provide basic instructions to ensure the comparison is
apples-to-apples with my measurements.

Personally, I think this should be done for every server, ever.  I see too
often, that other admins overload UPS's or circuit breakers, or waste money
by overprovision cooling or UPS's.  All of these are bad scenarios, and all
of them are easily avoidable for almost no cost, in terms of time or money.

For the heck of it, here are my "basic instructions," that I think should
always be habitually completed.

I use a kill-a-watt.  When the server is new, I write a 3-line python
script, which is an infinite loop of random number generation.  I launch as
many of these simultaneously as required, to fully max out all the CPU's.  I
measure both the VA and W consumption of the server, and record it all in a
spreadsheet.  I assume it's 120V, so you know the A by knowing the VA.  I
keep track of which servers are plugged into which UPS, and how many A are
available in the circuit feeding the UPS.  (I also measure the "charging"
current of the UPS.)  I always fluff everything by about 20%.  And I
estimate approx 3 BTU's cooling are required per W.

Many times before, I have also maxed out the disk, memory, or network
utilization, and consistently find that the idle power consumption equals
the fully active power.  It's only the CPU or GPU that seems to vary the
power consumption of the box significantly.

_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to