On 20/6/21 02:22, Ed Greshko wrote:
On 19/06/2021 21:44, Stephen Morris wrote:
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34
under a vm, that fedora does not have a swap specification in fstab
anymore, but is using, in my case, and 8GB swap partition in
/dev/zram0. Does this mean that if I create a swap partition of a
bigger size and specify it in fstab it will be ignored?
Ignored? No. But not primary. e.g.
[egreshko@meimei ~]$ swapon
NAME TYPE SIZE USED PRIO
/dev/sda2 partition 16.9G 0B -2
/dev/zram0 partition 4.7G 0B 100
So, it may or may not be used.
Alternatively, given the fedora is using it's own rules for
determining the swap size based on the amount of memory available,
is there any way to increase the size of /dev/zram0 so that there
is more swap space available to the system?
I think
man zram-generator
will help in that.
Thanks Ed, I'll check that man data out. In my case with an auto
storage configuration at F34 install time there isn't any swap entry
in fstab or swap partition. I think I need to expand this in
virtualbox as I think that virtualbox's lack of video memory is
causing performance issues in F34.
My system has been upgraded from versions without ZRAM. That is the
reason my system has a defined swap
partition on disk.
I don't see the connection between Video Memory and swap.
As I understand it, because I'm not using a dedicated graphics card the
video/graphics memory used by the vm is being sourced from real memory,
and I assume as part of the memory allocation being given to the vm,
hence would potentially increase the requirement for memory paging.
VirtualBox has a per-VM setting for its display and video memory. At
least that is the case for VirtualBox running
as a host on linux. I seem to recall you're using VirtualBox on HW
running Windows?
I am running Virtualbox on a Windows 10 host as I am running on a raid
10 motherboard supplied raid environment and Fedora workstation won't
install to raid (it can't see any devices), but having said that though,
Windows 10 can't see any devices to install to, but the motherboard bios
provides facilities to generate the necessary raid drivers to specify at
windows install time, but unfortunately it doesn't generate linux
drivers. The possible issue with video memory in virtualbox is the
windows version of virtualbox only allows a maximum of 128MB to be
allocated, which I think is no where near enough, hence the performance
issues. This is also why I'm still using Vmware player, as it allows
significantly more video memory allocation, and I was giving it 2GB of
video memory, but with that I was getting performance issues (I was
allocating 16GB of memory to the vm) and when I dropped the video memory
allocation back to the recommended of 768MB performance improved.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
