Hacker News new | ask | show | jobs
by mediocregopher 1567 days ago
If anyone has tried this on arch I'd love to hear your experience... I've got a home server sitting in my living room that looks bored.
3 comments

Been using lqx kernels for many years now.

On arch, I definitely get better gaming performance than the stock kernel. The liquorix repo's arch kernel doesn't play well with libvirt - that's about my only gripe.

Xanmod kernel seems to have all the gaming improvements and still plays nice with libvirt though.

Is there any meaningful difference between the two, other than the libvirt compat?
I run his kernel on my daily workstation at my day job :3 its stable and fantastic.

(Also run zen on my main gaming rig, another fantastic kernel)

Zen and Liquorix is the same, Liquorix is the "product" Zen is the tuning method:

>Zen Interactive Tuning: Tunes the kernel for responsiveness at the cost of throughput and power usage.

https://liquorix.net/#features

>Zen Kernel — Result of a collaborative effort of kernel hackers to provide the best Linux kernel possible for everyday systems. Some more details can be found on https://liquorix.net (which provides kernel binaries based on Zen for Debian).

https://wiki.archlinux.org/title/kernel

Be aware it's normally slower for server-workloads, but more responsive for Desktop-Stuff (Tunes the kernel for responsiveness at the cost of throughput and power usage), but on arch you can install it directly from the official sources (called zen-kernel there):

https://wiki.archlinux.org/title/kernel

> it's normally slower for server-workloads

I find this categorization of server workloads as something that is not latency sensitive bit weird. I'd imagine tons of server workloads that serve interactive users, for example a web server, should also care latency. If you for example are targeting <100ms p99 latency for your web service, then to me that sounds like it'd fall in the same ballpark as desktop use?

Sure there are still some batch workloads or other non-latency sensitive things around, but I'd almost expect those to be in the minority these days for servers.

Yes true, let's put it that way, "traditional" server-workloads.

>If you for example are targeting <100ms p99 latency for your web service.

Ah yes absolutely, if that needs that to be guaranteed maybe even real-time.