nanook

Not a fan of vim, it’s improper implementation of the ex command set and the way it ads line feeds, when you cut-n-paste between windows, makes it basically useless. I much prefer the BSD derived nvi, even on Linux. Like VIM it also handles multiple byte character sets, but UNLIKE VIM it is a COMPLETE and CORRECT implementation of vi/ex not a half-assed kind of sort of implementation.

Only situation where I’d consider including this in a kernel is for use on a gaming platform where it could enable kernel based anti-cheats and thus be attractive to game developers that would otherwise avoid Linux.

I will add to all of this, which is basically good advice, also MONITOR how changes you make affect performance, use tools like glances, btop, iotop, top, free, to monitor various system parameters and modern kernels really do help a lot. I saw wait time go down quite a bit with 6.14 relative to 6.13, granted this is an environment with around 1000 simultaneous processes and even more threads, but I think it will help most loads. But bottom line, measure, measure, and then measure.

Even if you’re not swapping, more RAM means more buffer and cache. 32GB isn’t all that much, I’ve got 96GB in my workstation and 256GB in the server that runs friendica.

If you are running Linux, I would recommend maxing out the amount of RAM that your CPU supports. Memory I/O is faster than the fastest SSD, and Linux will use all RAM not being used for something else for buffers and cache putting write in the background so you don’t have to wait upon them. Also consider using a modern kernel and tailoring it to your processor, use the -march argument for your architecture in the compile, this will utilize your CPU to it’s fullest.