[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-dj77OzDKmcaVFJVdUyPv6rgWg0eLFGubDKTi8OgEH3o":3,"sanity-irZIK4JbYpo3C0PGZgHEkuaNmh9tACbPFcr1AEA_Q8o":217},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":192},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"5c7f0882-e1a7-4d0e-9e06-86cce9c3613a","2026-07-02T07:40:00.000Z",{"_type":10,"current":11},"slug","ai-coding-chaos-into-a-repeatable-playbook",null,"How do you turn AI coding chaos into a repeatable playbook?",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":58,"comments":169,"dateUrl":170,"excerpt":171,"image":172,"legacyBody":176,"product":12,"publishedAt":179,"slug":180,"sponsored":12,"tags":182,"title":191,"visible":169},"2023-05-25T09:39:09Z","wp-post-5236","dgl3SCUzppW3U2LvCoSN08","blogPost","2023-07-13T14:55:03Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":54,"name":55,"slug":56},"2023-05-23T16:27:18Z","wp-author-139","07ZbrKPSUrjrV4wQ6fampK","blogAuthor","2023-08-29T11:49:13Z",{"_type":53},"image","former","Nick Craver",{"current":57},"nickcraver",[59,119,128],{"_key":60,"_type":61,"children":62,"markDefs":112,"style":118},"1aa33fda6a49","block",[63,68,73,77,81,85,91,95,100,104,108],{"_key":64,"_type":65,"marks":66,"text":67},"1aa33fda6a490","span",[],"Who loves hardware? Well, I do. If you ",{"_key":69,"_type":65,"marks":70,"text":72},"1aa33fda6a491",[71],"em","don't",{"_key":74,"_type":65,"marks":75,"text":76},"1aa33fda6a492",[]," love hardware then I'd go ahead and close the browser. Still here? Awesome. Or your browser is crazy slow, in which case you should think about some new hardware. I've repeated many, ",{"_key":78,"_type":65,"marks":79,"text":80},"1aa33fda6a493",[71],"many",{"_key":82,"_type":65,"marks":83,"text":84},"1aa33fda6a494",[]," times: ",{"_key":86,"_type":65,"marks":87,"text":90},"1aa33fda6a495",[88,89],"strong","8ca673c5ef58","performance is a feature",{"_key":92,"_type":65,"marks":93,"text":94},"1aa33fda6a496",[],". Since your code is only as fast as the hardware it runs on, the hardware definitely matters. Just like any other platform, Stack Overflow's architecture comes in layers. Hardware is the foundation layer for us, and having it in-house affords us many luxuries not available in other scenarios...like running on someone else’s servers. It also comes with direct and indirect costs. But that's not the point of this post, ",{"_key":96,"_type":65,"marks":97,"text":99},"1aa33fda6a497",[98],"c32b4061bec7","that comparison will come later",{"_key":101,"_type":65,"marks":102,"text":103},"1aa33fda6a498",[],". For now, I want to provide a detailed inventory of our infrastructure for reference and comparison purposes. And pictures of servers. Sometimes naked servers. This web page could have loaded much faster, but I couldn't help myself. In many posts through this series I will give a lot of numbers and specs. When I say \"our SQL server utilization is almost always at 5--10% CPU,\" well, that's great. But, 5--10% ",{"_key":105,"_type":65,"marks":106,"text":107},"1aa33fda6a499",[71],"of what?",{"_key":109,"_type":65,"marks":110,"text":111},"1aa33fda6a4910",[]," That's when we need a point of reference. This hardware list is meant to both answer those questions and serve as a source for comparison when looking at other platforms and what utilization may look like there, how much capacity to compare to, etc.",[113,116],{"_key":89,"_type":114,"href":115,"reference":12},"link","http:\u002F\u002Fblog.codinghorror.com\u002Fperformance-is-a-feature\u002F",{"_key":98,"_type":114,"href":117,"reference":12},"https:\u002F\u002Ftrello.com\u002Fc\u002F4e6TOnA7\u002F87-on-prem-vs-aws-azure-etc-why-the-cloud-isn-t-for-us","normal",{"_key":120,"_type":61,"children":121,"markDefs":126,"style":127},"e51caf065d5e",[122],{"_key":123,"_type":65,"marks":124,"text":125},"e51caf065d5e0",[],"How We Do Hardware",[],"h2",{"_key":129,"_type":61,"children":130,"markDefs":162,"style":118},"72e70a771406",[131,135,140,144,149,153,158],{"_key":132,"_type":65,"marks":133,"text":134},"72e70a7714060",[],"Disclaimer: I don't do this alone. George Beech (",{"_key":136,"_type":65,"marks":137,"text":139},"72e70a7714061",[138],"b8b2219d89a0","@GABeech",{"_key":141,"_type":65,"marks":142,"text":143},"72e70a7714062",[],") is my main partner in crime when speccing hardware here at Stack. We carefully spec out each server for its intended purpose. What we don't do is order in bulk and assign tasks later. We're not alone in this process though; you have to know what's going to run on the hardware to spec it optimally. We'll work with the developer(s) and\u002For other site reliability engineers to best accommodate what is intended live on the box. Read the rest of ",{"_key":145,"_type":65,"marks":146,"text":148},"72e70a7714063",[147],"63a729e4e753","Stack Overflow: The Hardware - 2016 Edition on Nick's blog here",{"_key":150,"_type":65,"marks":151,"text":152},"72e70a7714064",[],". It's the second in an ",{"_key":154,"_type":65,"marks":155,"text":157},"72e70a7714065",[156],"f2af3a0d9d07","extensive series",{"_key":159,"_type":65,"marks":160,"text":161},"72e70a7714066",[]," of blog posts on Stack Overflow’s technical architecture.",[163,165,167],{"_key":138,"_type":114,"href":164,"reference":12},"https:\u002F\u002Ftwitter.com\u002FGABeech",{"_key":147,"_type":114,"href":166,"reference":12},"https:\u002F\u002Fnickcraver.com\u002Fblog\u002F2016\u002F03\u002F29\u002Fstack-overflow-the-hardware-2016-edition\u002F",{"_key":156,"_type":114,"href":168,"reference":12},"https:\u002F\u002Fnickcraver.com\u002Fblog\u002F2016\u002F02\u002F03\u002Fstack-overflow-a-technical-deconstruction\u002F",true,"2016\u002F03\u002F29","",{"_type":53,"asset":173},{"_ref":174,"_type":175},"image-c1c44f574f53e1a68e16134cc3b33690d6aceeae-1920x1080-png","reference",{"code":177,"language":178},"Who loves hardware? Well, I do. If you \u003Cem>don't\u003C\u002Fem> love hardware then I'd go ahead and close the browser.\n\nStill here? Awesome. Or your browser is crazy slow, in which case you should think about some new hardware.\n\nI've repeated many, \u003Cem>many\u003C\u002Fem> times: \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fblog.codinghorror.com\u002Fperformance-is-a-feature\u002F\">performance is a feature\u003C\u002Fa>\u003C\u002Fstrong>. Since your code is only as fast as the hardware it runs on, the hardware definitely matters. Just like any other platform, Stack Overflow's architecture comes in layers. Hardware is the foundation layer for us, and having it in-house affords us many luxuries not available in other scenarios...like running on someone else’s servers. It also comes with direct and indirect costs. But that's not the point of this post, \u003Ca href=\"https:\u002F\u002Ftrello.com\u002Fc\u002F4e6TOnA7\u002F87-on-prem-vs-aws-azure-etc-why-the-cloud-isn-t-for-us\">that comparison will come later\u003C\u002Fa>. For now, I want to provide a detailed inventory of our infrastructure for reference and comparison purposes. And pictures of servers. Sometimes naked servers. This web page could have loaded much faster, but I couldn't help myself.\n\nIn many posts through this series I will give a lot of numbers and specs. When I say \"our SQL server utilization is almost always at 5--10% CPU,\" well, that's great. But, 5--10% \u003Cem>of what?\u003C\u002Fem> That's when we need a point of reference. This hardware list is meant to both answer those questions and serve as a source for comparison when looking at other platforms and what utilization may look like there, how much capacity to compare to, etc.\n\n\u003Ch2>How We Do Hardware\u003C\u002Fh2>\n\nDisclaimer: I don't do this alone. George Beech (\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002FGABeech\">@GABeech\u003C\u002Fa>) is my main partner in crime when speccing hardware here at Stack. We carefully spec out each server for its intended purpose. What we don't do is order in bulk and assign tasks later. We're not alone in this process though; you have to know what's going to run on the hardware to spec it optimally. We'll work with the developer(s) and\u002For other site reliability engineers to best accommodate what is intended live on the box.\n\nRead the rest of \u003Ca href=\"https:\u002F\u002Fnickcraver.com\u002Fblog\u002F2016\u002F03\u002F29\u002Fstack-overflow-the-hardware-2016-edition\u002F\">Stack Overflow: The Hardware - 2016 Edition on Nick's blog here\u003C\u002Fa>. It's the second in an \u003Ca href=\"https:\u002F\u002Fnickcraver.com\u002Fblog\u002F2016\u002F02\u002F03\u002Fstack-overflow-a-technical-deconstruction\u002F\">extensive series\u003C\u002Fa> of blog posts on Stack Overflow’s technical architecture.","html","2016-03-29T12:00:00.000Z",{"current":181},"stack-overflow-the-hardware-2016-edition",[183],{"_createdAt":184,"_id":185,"_rev":186,"_type":187,"_updatedAt":184,"slug":188,"title":190},"2023-05-23T16:43:21Z","wp-tagcat-engineering","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":189},"engineering","Engineering","Stack Overflow: The Hardware - 2016 Edition",[193,199,205,211],{"_id":194,"publishedAt":195,"slug":196,"sponsored":12,"title":198},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":197},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":200,"publishedAt":201,"slug":202,"sponsored":12,"title":204},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":203},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":206,"publishedAt":207,"slug":208,"sponsored":12,"title":210},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":209},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":212,"publishedAt":213,"slug":214,"sponsored":12,"title":216},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":215},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":218,"sourceMap":-1},{"count":219,"lastTimestamp":220},1,"2023-05-25T09:45:54Z"]