Re:Lichess gets a big upgrade. It doesn't go as planned
by boarquantile on Saturday December 17, 2022 @02:17PM
(#34031139)
Load testing would have to be quite advanced to find this, doing more than just simulating users for the most common features. It took more than 24 hours of real-world usage to visit sufficiently many niche code paths to fill the code cache.
Re:Lichess gets a big upgrade. It doesn't go as planned
by bravetraveler on Saturday December 17, 2022 @04:07PM
(#34032245)
Advanced in that it's POST instead of GET, and some parameters to boot
I'm not saying it doesn't take effort, I'm just saying it can and is regularly done
Regression testing with speed. If you test your features as they're added, niche-ness doesn't matter - you know about it and test it
A regression test quickly turns into a load test if you do them all at once
To be clear, I'm not trying to twist the knife. I understand why it wouldn't be done. I just won't pretend it can't
I've been trying to avoid this 'hindsight is 20/20' thing...
I'm not trying to lay blame - just offer thoughts towards improvement, and encouragement against some defeatist thinking patterns
A lot can be done with very little equipment/time investment
Think about it - clients or requests are really just ephemeral ports...
There are something like 30 thousand of them available by default with Linux
If you use sockets you can have as many connections as your system allows for open file descriptors. The upward limit is...
Spawn a ton of concurrent requests to hit the service/API! apachebench is a decent example of the idea - imagine some proprietary sauce with itIt gets cheaper (and in some ways, more effective) if you actually remove the network -- latency goes down
You can also rate limit it in software, but it's really not analogous in some ways (eg: net.core.somaxconn limitations/realities)
Development time is totally understandable though. It's important I leave my green field of comfort