Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

swap on zvol causes high system latency when memory pressure occurs #9435

Closed
codyps opened this issue Oct 9, 2019 · 2 comments
Closed

swap on zvol causes high system latency when memory pressure occurs #9435

codyps opened this issue Oct 9, 2019 · 2 comments
Labels
Status: Stale No recent activity for issue

Comments

@codyps
Copy link

codyps commented Oct 9, 2019

System information

Type Version/Name
Distribution Name arch
Distribution Version 2019-10-09
Linux Kernel 5.3.1-arch1-1-ARCH
Architecture x86_64
ZFS Version zfs-0.8.2-1

Describe the problem you're observing

When using a zvol as swap, if something pushes ram usage higher (for example, starting a virtual machine), then high system latency (visible in Xorg) occurs: display stops updating, mouse stops moving, keyboard stops responding. Latency in ssh sessions appears minimal. When the swap device is removed (swapoff), the system behavior returns to normal (even with the memory consuming application still running).

Describe how to reproduce the problem

zfs create -V 4G -b $(getconf PAGESIZE) -o compression=zle -o logbias=throughput -o sync=always -o primarycache=metadata -o secondarycache=none -o com.sun:auto-snapshot=false ${ZFS}/swap
mkswap /dev/zvol/${ZFS}/swap
swapon /dev/zvol/${ZFS}/swap
# perform enough zfs access & run applications so that memory is almost filled
# start something that allocates enough memory so that zfs would need to flush some pages from the ARC (this is a presumption given the behavior. I'm starting VirtualBox vms with 8GiB of ram allocated to them)

Include any warning/errors/backtraces from the system logs

No warnings/errors/etc in system logs from this timeframe

@devZer0
Copy link

devZer0 commented Oct 22, 2019

#7734

@stale
Copy link

stale bot commented Oct 21, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Oct 21, 2020
@stale stale bot closed this as completed Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale No recent activity for issue
Projects
None yet
Development

No branches or pull requests

2 participants