3 ms·
Oh, it isn’t always play - sometimes you discover that you are IO bound when you shouldn’t be, and end up tracing your woes through a similar route to that whic
by madaxe_again 3y ago
Oh, it isn’t always play - sometimes you discover that you are IO bound when you shouldn’t be, and end up tracing your woes through a similar route to that which you describe to a bug in the hypervisor scheduler where network and disk IO are blocking each other due to a shared interrupt specific to the combination of disk controller and silicon that’s running the kernel. You blow a day of engineering time, but you improve performance of your product by an order of magnitude on the same hardware.
- sgarland 3y agoThat would be amazingly fun for me! Did you happen to file a bug report somewhere publicly? I’d love to read more about it.
- madaxe_again 3y agoNo, as it was a configuration issue down to the VPS provider, who are now huge but at the time were just starting out, and a known issue - we coached them through fixing it. I do have bug reports and patches floating around for all sorts of other arcane stuff, from drivers to the Linux kernel to memcached to nginx - most of which are from 10-15 years ago now, as I ended up bogged down running the business. These days The Understanding is instead deployed for living off grid and making infrastructure work.