A Rack of One's Own

Line 1:

~~<b>~~dankblog! 2023-03-11, 1709 EST, at the danktower~~</b>~~

'''[[Dankblog|dankblog!]] 2023-03-11, 1709 EST, at [[Viewpoint|the danktower]]'''

i've never owned "enterprise-class" hardware, nor even really worked with it much. i'm of the Google school: buy COTS by lots, count on it breaking, and work around the failures. xeons and (more recently) epycs never seemed price-competitive (though i seriously considered the former for my [[Schwarzger%C3%A4t|2016 workstation build]]), especially given their reduced clocks. as amd's threadripper emerged, they weren't even holding it down on core count--only recently has sapphire rapids matched my 3970x's dotriacontacore setup (13th generation intel core processors topped out at 24 cores), and they still can't match that marvelous processor's LLC sizes. it just didn't make sense. the available motherboards furthermore always seemed a few years behind with regards to USB. if you didn't intend to take advantage of those fat support deals, the only value proposition seemed to be support for massive amounts of (ECC!) memory, and the server processors' heftier memory controllers (threadripper's cap at four memory controllers was the major reason why i went with a 3970X rather than the 64-core 3990X--how is one supposed to keep all those cores fed with only four DDR4 controllers?).

A Rack of One's Own: Difference between revisions

Dank (talk | contribs)

Revision as of 00:31, 12 March 2023 view source Dank (talk \| contribs) Bureaucrats, Administrators 11,302 edits No edit summary ← Older edit		Revision as of 00:48, 12 March 2023 view source Dank (talk \| contribs) Bureaucrats, Administrators 11,302 edits No edit summary Newer edit →
Line 1:		Line 1:
	~~<b>~~dankblog! 2023-03-11, 1709 EST, at the danktower~~</b>~~		'''[[Dankblog\|dankblog!]] 2023-03-11, 1709 EST, at [[Viewpoint\|the danktower]]'''

	i've never owned "enterprise-class" hardware, nor even really worked with it much. i'm of the Google school: buy COTS by lots, count on it breaking, and work around the failures. xeons and (more recently) epycs never seemed price-competitive (though i seriously considered the former for my [[Schwarzger%C3%A4t\|2016 workstation build]]), especially given their reduced clocks. as amd's threadripper emerged, they weren't even holding it down on core count--only recently has sapphire rapids matched my 3970x's dotriacontacore setup (13th generation intel core processors topped out at 24 cores), and they still can't match that marvelous processor's LLC sizes. it just didn't make sense. the available motherboards furthermore always seemed a few years behind with regards to USB. if you didn't intend to take advantage of those fat support deals, the only value proposition seemed to be support for massive amounts of (ECC!) memory, and the server processors' heftier memory controllers (threadripper's cap at four memory controllers was the major reason why i went with a 3970X rather than the 64-core 3990X--how is one supposed to keep all those cores fed with only four DDR4 controllers?).		i've never owned "enterprise-class" hardware, nor even really worked with it much. i'm of the Google school: buy COTS by lots, count on it breaking, and work around the failures. xeons and (more recently) epycs never seemed price-competitive (though i seriously considered the former for my [[Schwarzger%C3%A4t\|2016 workstation build]]), especially given their reduced clocks. as amd's threadripper emerged, they weren't even holding it down on core count--only recently has sapphire rapids matched my 3970x's dotriacontacore setup (13th generation intel core processors topped out at 24 cores), and they still can't match that marvelous processor's LLC sizes. it just didn't make sense. the available motherboards furthermore always seemed a few years behind with regards to USB. if you didn't intend to take advantage of those fat support deals, the only value proposition seemed to be support for massive amounts of (ECC!) memory, and the server processors' heftier memory controllers (threadripper's cap at four memory controllers was the major reason why i went with a 3970X rather than the 64-core 3990X--how is one supposed to keep all those cores fed with only four DDR4 controllers?).