What is going on with Cooker release? It loads in 12-15 seconds to desktop in vmware Worskation on Windows while Rome takes 30+ seconds. The whole DE seems more responsive too. Is it supposed to be this fast on real hardware for both Rome and Cooker (I mean Rome only slow in VM)? Or Rome is just have some “unoptimized” software at the moment?
Welcome. It goes without saying (but I’m going to say it anyway) that we don’t support vmware since it’s a proprietary solution. This means your performance may vary and we won’t be able to assist with it.
I can say that the difference between the two is probably the kernel. Cooker is our development release, while ROME is the last stable Cooker before we started updating to newer releases from the upstreams.
In addition to what Zeroability said here the are other things to consider re VM linux client performance:
- mesa: Rome has 25.0.7, while Cooker has 25.1.5
- Xorg vs Wayland (you don’t say what session you are running on the client…)
- Xorg (Rome) vs Xlibre (Cooker): nobody tested if the performance for the latter changes
- Verify that both VMs don’t blacklist the linux driver (the default)
- …
Obviously YMMV.
Even in some other distros I have seen HUGE gains in boot times from the newer systemd versions. They are even beating SysV now.
Actually Virtual Box is very slow. It loads same Cooker release about 1 minute (!) and 12 seconds. I use x11 as suggested by default, znver. Hypervisor and all other stuff that make vmware slow are disabled. Vmware is only missing open-vm-tools, I dont really care about proprietary or not.
(figured out Extra repo have open-vm-tools)
Try the x86_64 flavor, instead.
On vmware x86-64 is around the same.I figured out x11-driver-video-vmware makes loading much slower, from 10-15s to 30-40s.
BTW I want to toy around on real hardware. Rome release, I will check if my crucial VST plugins are working. Should I install znver? CPU is Ryzen 5800x