Date: Sat, 12 Aug 2017 11:09:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O Message-ID: <bug-220971-8-mcThIhszUi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220971-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220971-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220971 --- Comment #6 from Mark Millard <markmi@dsl-only.net> --- (In reply to execve from comment #4) FYI since you have more RAM than the original context for that stress command I'll quote from the man page: -m, --vm N spawn N workers spinning on malloc()/free() --vm-bytes B malloc B bytes per vm worker (default is 256MB) -d, --hdd N spawn N workers spinning on write()/unlink() --vm-keep redirty memory instead of freeing and reallocating So: stress -d 2 -m 3 --vm-keep is only doing 3*256MB =3D 768MB of VM use. That was a large percentage of the 1GB of RAM that the related bugzilla 206048 indicated as the context for the command. It is not that much of around 8GiBytes of RAM. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220971-8-mcThIhszUi>