Saving Three Months of Latency with a Single OpenTelemetry Trace

Re:Saving Three Months of Latency with a Single OpenTelemetr... by redman25 on Friday June 07, 2024 @01:31PM (#40610855)

I often ask myself the same question. We have some user facing queries that slow the frontend down. I’ve fixed some slowness but it’s definitely not a priority. I wonder how much speed improvements correlate with increased revenue by happy customers.

[ Parent | on HN ]

Re:Saving Three Months of Latency with a Single OpenTelemetr... by encoderer on Friday June 07, 2024 @01:55PM (#40611102)

Think of this like changing the oil in your car.

Over-optimizing is not going to help you at all but if you ignore it eventually it will all seize up.

You have to keep that stuff in check.

[ Parent | on HN ]

Re:Saving Three Months of Latency with a Single OpenTelemetr... by drakir_nosslin on Monday June 10, 2024 @11:02AM (#40634387)

Bit late to the party, but companies report that webpage speed correlates with conversion. See e.g. https://www.cloudflare.com/en-gb/learning/performance/why-si... & https://www.cloudflare.com/en-gb/learning/performance/more/w...

This one is also interesting; written in 2012, it claims that Amazon could lose 1b+ from a 1 sec slowdown: https://www.fastcompany.com/1825005/how-one-second-could-cos.... I imagine people are even less tolerant of slow pages today.

Fixing website performance can be one of the cheapest ways to increase conversion because it's hard to figure out what else moves the needle.

[ Parent | on HN ]