Alexander Slesarev

Results 45 comments of Alexander Slesarev

The issue does exist, and it was an originally a bug in mingw: https://sourceforge.net/p/mingw/mailman/mingw-users/thread/da6ae25705030719572e9601f2%40mail.gmail.com/ They provide the implementation (https://github.com/mirror/mingw-w64/blob/master/mingw-w64-crt/libsrc/ws2tcpip/gai_strerrorA.c), I guess Zig should do the same.

Rust/Rocket is already used in the production mode. Moreover, I've added an option (`-p`) to start the sample in the "vanilla" production mode (before the change, the number of workers...

I tried few combinations (8, 16) and all of them got stuck. Considering that `hey` uses 256 concurrent connections in the tests, I've decided to use 256 workers too -...

Not really, the raw results are analyzed by the Ruby script that generates Markdown tables inserted into README. However, I can publish the raw results, so they could be analyzed...

Energy reading comes from the file `/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj` and @kostya is right, it's Intel specific. AMD supports RAPL too (https://web.eece.maine.edu/~vweaver/projects/rapl/rapl_support.html) but requires different API to use. Unfortunately, I don't have AMD...

The metrics (not formula though) you've described fits the value we already have - Energy. For Intel RAPL (https://blog.chih.me/read-cpu-power-with-RAPL.html) the whole (package) energy consumption is based on CPU (PP0), GPU...

Please dismiss my notes about current implementation not supporting whole package. It reads `/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj` that is the whole package (with PP0 etc are within that directory, e.g. `/sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:0/energy_uj `). I...

Right, energy consumption doesn't necessary correlate to RAM usage (I guess the correlation could be caused by more CPU work that could be unaccounted for as we track only the...

If there are some leaks, then I'd prefer them to be fixed. I don't have any preferences regarding automatic vs manual though, so if you're willing to address it, that...

@beached That's a tricky one. Officially, it's just a performance regression on Intel processors, not a "defect", and could be eventually fixed by the microcode update. However, I have the...