| ▲ | bgirard 5 days ago |
| > Identifying a representative usage scenario to optimize towards and then implementing that scenario in a microbenchmark test driver are both massively difficult to get right, and a "failure" in this regard, as the author found, can be hard to detect before you sink a lot of time into it. I can vouch for this. I've been doing web performance for nearly 15 years and finding clear representative problems is one the hardest parts of my job. Once I understood this and worked on getting better at finding representative issues, it became the single thing that I did to boost my productivity the most. |
|
| ▲ | jasonthorsness 5 days ago | parent | next [-] |
| What have you found are the most useful approaches to collecting the representative issues in a way you can reuse and test? I haven’t worked as much in the web space. |
| |
| ▲ | bgirard 5 days ago | parent [-] | | A combination of: 1) RUM, 2) Field tracing, 3) Local tracing with throttling (CPU, Network), 4) Focusing either on known problems, or if I'm on less certain territory I will do more vetting to make sure I'm chasing something real. I'll minimize the time spent on issues that I can only catch in one trace, but sometimes it's also all you get so I'll time box that work carefully. It's more of an art than a science. |
|
|
| ▲ | viraptor 5 days ago | parent | prev [-] |
| Tracing and continuous profiling made this task significantly easier than it was in the past, fortunately. |
| |
| ▲ | bgirard 5 days ago | parent | next [-] | | It's great. Much harder on Web because it's difficult to get rich information from the browser. This is why I contributed to the JS Self-Profiling API in the first place: https://developer.mozilla.org/en-US/docs/Web/API/JS_Self-Pro... | |
| ▲ | CodesInChaos 5 days ago | parent | prev [-] | | Can your recommend tools for continuous profiling? I'm mainly interested in Rust and C# on Linux. I'm not sure if it has gotten easier. Async is harder to profile than classic threaded code using blocking IO. And for database bound code, I'm not sure which databases output detailed enough performance information. | | |
|
