You can see your pool driver by executing `qvm-pool`.
And the latest version of my scripts will always be available at [1].
Btw somehow one gets used to the worse performance after a while...
[1]
https://github.com/3hhh/qubes-performance
Mine currently looks like this:
Qubes release 4.1 (R4.1)
dom0 kernel: 5.10.109-1.fc32.qubes.x86_64
dom0 Xen: 4.14.5
VM kernel: 5.15.52-1.fc32
Xen:
qrexec startup: 240 ms
Qubes DB: 8800 ms
VM handover: 8901 ms
Linux:
kernel: 4480 ms
system: 4298 ms
user: 178 ms
system critical-chain:
multi-user.target @4.298s
└─qubes-qrexec-agent.service @4.164s +133ms
└─systemd-user-sessions.service @4.102s +31ms
└─network.target @4.092s
└─qubes-network-uplink.service @2.638s +1.447s
└─basic.target @2.544s
└─sockets.target @2.544s
└─dbus.socket @2.542s
└─sysinit.target @2.531s
└─systemd-update-utmp.service @2.482s +47ms
└─systemd-tmpfiles-setup.service @2.349s +122ms
└─local-fs.target @2.317s
└─run-user-1000.mount @4.773s
└─local-fs-pre.target @1.427s
└─systemd-tmpfiles-setup-dev.service @1.150s +276ms
└─systemd-sysusers.service @1.090s +58ms
└─systemd-remount-fs.service @1.006s +80ms
└─systemd-fsck-root.service @771ms +233ms
└─systemd-journald.socket @572ms
└─-.mount @519ms
└─-.slice @519ms
qrexec service critical-chain:
qubes-qrexec-agent.service +133ms
└─systemd-user-sessions.service @4.102s +31ms
└─network.target @4.092s
└─qubes-network-uplink.service @2.638s +1.447s
└─basic.target @2.544s
└─sockets.target @2.544s
└─dbus.socket @2.542s
└─sysinit.target @2.531s
└─systemd-update-utmp.service @2.482s +47ms
└─systemd-tmpfiles-setup.service @2.349s +122ms
└─local-fs.target @2.317s
└─run-user-1000.mount @4.773s
└─local-fs-pre.target @1.427s
└─systemd-tmpfiles-setup-dev.service @1.150s +276ms
└─systemd-sysusers.service @1.090s +58ms
└─systemd-remount-fs.service @1.006s +80ms
└─systemd-fsck-root.service @771ms +233ms
└─systemd-journald.socket @572ms
└─-.mount @519ms
└─-.slice @519ms
qubes.GetDate: n/a
qubes.WindowIconUpdater: n/a
qrexec service: 4102 ms
qrexec (1st run):
exec time: 4602 ms (depends on clock sync)
return: 5479 ms
qrexec (2nd run):
exec time: -105 ms (depends on clock sync)
return: 782 ms
Overall: 23202 ms (excl. 2nd qrexec run)