republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
866
Share Topic
Posting?
Post a:
Post a:
Links: ·Seti@Home ·S@H Enhanced FAQ ·S@H Enhanced Application FAQ ·Join Our Team
AuthorAll Replies


KoshVorlon
B B R
Premium,Mod
join:2000-06-28
Babylon 5
Host:
Team Starfire
Midwest

Too bad this has to go right into production . . .

Click for full size
Big System
Cisco UCS B440 M2 Blade Server
4 Processors - Intel Xeon E74860
- 40 Cores - 80 Threads
512 GB RAM - 32 @ 16 GB DIMM


leibold
Premium,MVM
join:2002-07-09
Sunnyvale, CA
kudos:6
Reviews:
·SONIC.NET

There should always be time to do some burn-in testing for a new production system. Even if it is only a couple of days. If you look any server life analysis with decent sample size you will find a good number of early failures followed by a couple of years with very low failure rates before the rate of age and wear related failures starts to rise again. The purpose of burn-in testing is to flush out those early failures so that they do not happen in production.

I'm sure you know that distributed computing apps are great for burn-in testing
--
Got some spare cpu cycles ? Join Team Helix or Team Starfire!



CylonRed
Premium,MVM
join:2000-07-06
Bloom County

reply to KoshVorlon
mmmmmm - hardware porn...


Wednesday, 22-May 23:49:19 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics