all_your_base VS profiler

And then I had a toy project this summer making a base64 en/decoder cli tool. That was great. Improved a bit on it every day, learned many new details of the language and actually got a pretty good tool out of it, https://github.com/skovmand/all_your_base

The only change for the performance increase is this commit: https://github.com/skovmand/all_your_base/commit/9f83f8669148b43cf17760ed2832196854976ff5

The first test in https://github.com/skovmand/all_your_base/blob/cli_tests/tests/cli.rs was meant to test that it reads stdin from the outside. There's a lot of unit tests in the library code already at https://github.com/skovmand/all_your_base/blob/cli_tests/src/encoder.rs#L152 and forward.

Probably your best bet is to use the Firefox Profiler once it starts hogging the CPU to try to see what it's doing. I'd be happy to take a look at the result although I don't have a lot of experience at diagnosing performance problems; hopefully the profile will make it obvious what's going on.

I tried using the https://profiler.firefox.com/ and running with:

You can try to reproduce while taking a profile using the Firefox profiler, then share it in the #perf:mozilla.org room on Mozilla's Matrix instance.

Run a profiling session for ~30 sec when you notice something is running slower than you expect, see https://profiler.firefox.com/. Share results here if you want help interpreting them.

Next time, send a SIGABRT to the main process (kill -6 $(pidof firefox)) and use the resulting backtrace (you will find a link to the crash report in about:crashes) to file a bug. A performance profile could be useful, but you'll need to know first what to capture. This seems like a graphics issue, so try the Graphics preset. Share a link to your report.

https://profiler.firefox.com will be useful if you can capture and share it to developers.

If you can reproduce it in safe mode and a clean profile, capture a performance profile using the clean profile while trying to load a problematic webpage, don't remove any information from it, and share it here (although it's typically not easy for users to analyse them), or file a bug with it attached.

Next time, capture a performance profile using the Graphics preset, and kill the browser by entering kill -6 $(pidof firefox) in a shell. This will create a bug report (unless debian disables the crash reporter) that would indicate where Firefox is stuck at. You might need to use an official build to get useful results.