3 ms·

That's a prime example of survivorship bias, projects that spent their runway optimizing for machine resources are not around to have their problems recognized.

• p_l 7y ago
  I had more than one project where people were cheaper than machines, and going tight on budgets for machine resources led to the project surviving instead of dying. Hell, a big example of that is Stack Overflow, which runs a very busy site on much less hw than they would have needed otherwise, just by taking high level optimization questions up front.
  • seemslegit 7y ago
    And can you spot a non json/http based service in their stack ? (no redis and sqlserver don't count because they don't own those) https://nickcraver.com/blog/2016/02/17/stack-overflow-the-architecture-2016-edition/ https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar... don't know if there's a later one. EDIT: I see they store their redis values in protobuf which is probably more due to memory utilization rather than serialization performance concerns
    • p_l 7y ago
      I can spot, however, kernel-mode HTTP servers (including customized ones), and heavy use of pretty advanced stack with good optimization capabilities. The choices of the stack do make a big impact, something that they have mentioned several times, with the summary of "paying Microsoft licenses paid back very well compared to using popular open-source stacks" Remember, Performance is also a feature. Both a non-functional one (to reduce your costs) or functional one (to have happier users).