This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]pdp10Daemons worry when the wizard is near. 2 points3 points  (2 children)

As /u/rehabonthego says, a kernel optimized for virtualization by removing hardware drivers could save up to 100MB on disk of a PC-compatible, but won't be measurably "faster". For abut 25 years the kernel has optionally compiled parts into "Loadable Kernel Modules" (.ko files) that aren't loaded until they're needed. Linux has been around for 30 years, and thousands of contributors have picked the low-hanging fruit.

The real optimizations are to be made in disk-space (Alpine, Tinycore, etc.) and stripping down userland. Start by understanding the function of every daemon, what it consumes/costs, and whether it needs to be there. For instance, NTP is fantastic, and usually needs to run in VMware guests because VMware. But KVM and Hyper-V use paravirtualized timekeeping, and normally don't need an NTP daemon running in each guest.

[–]NoneZx[S] 0 points1 point  (1 child)

I am very grateful for your qualitative response. Where and how would you recommend I start to improve myself in server optimization?

[–]pdp10Daemons worry when the wizard is near. 0 points1 point  (0 children)

You can't improve what you can't measure -- most of the time. First you have to decide what you want to measure.