4 ms·
Very curious to learn more about what the monolith was doing so incredibly poorly that you managed to squeeze that much performance out of it. Poorly written qu
by smarkov 3y ago
Very curious to learn more about what the monolith was doing so incredibly poorly that you managed to squeeze that much performance out of it. Poorly written queries? Too many queries? Lack of any caching? Doing things synchronously when they could've been done concurrently?
- porridgeandrice 3y ago+1 I'd like to know as well
- justinlloyd 3y agohttps://justinlloyd.li/blog/how-much-cache-you-got-on-you/ https://justinlloyd.li/blog/how-much-cache-you-got-on-you/
- justinlloyd 3y agoSome of that, some other bad practices. Lots of low-hanging fruit, then more esoteric changes. https://justinlloyd.li/blog/how-much-cache-you-got-on-you/ https://justinlloyd.li/blog/how-much-cache-you-got-on-you/
- zepolen 3y agoHe cached everything and delayed writes too. It's easy to make a system fast when it's not realtime.
- justinlloyd 3y agoIncredibly dismissive of somebody's work, aren't ya? I regret breaking my own self-imposed rule of never answering follow-up questions on HN because there's always somebody willing to hand-wave away six months of my life and 40 years of real-world experience with a flippant comment of "oh, but that's easy if you don't have too..."
- zepolen 3y agoFragile ego too.
- justinlloyd 3y agoAnd you sir, are fucking toxic, just looking at your comment history I can tell that. So you calling me "fragile" carries about as much weight as the next idiot with an opinion.
- zepolen 3y agoToxicity is in the eye of the beholder.
- deleted 3y ago[deleted]
- high_priest 3y agoQuick google yields very good examples in huge improvements on a single algorithm level: https://youtu.be/c33AZBnRHks https://youtu.be/c33AZBnRHks Easy to imagine how even smaller improvements across 10-100 steps of data processing, can become even better.