https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282994

--- Comment #6 from jsml4thwwbid6...@protonmail.com ---
(In reply to Mark Johnston from comment #5)

A user-land program crashing because of not having enough resources is
acceptable. I can always add more resources when needed. It's a hosting
environment with non-trusted users, so resource controls are pretty important
to maintain system stability. 

The rctl rules only apply to user ids 5000+. Everything below that is not
covered by rctl. Here's an example of top being slow to launch. 

root@compute03:~ # top
load: 18.74  cmd: top 61547 [sysctl mem] 2.25r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 3.21r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 3.77r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 4.54r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 4.88r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 5.40r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 6.35r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 6.57r 0.00u 0.00s 0% 3212k
load: 18.12  cmd: top 61547 [sysctl mem] 7.15r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 9.09r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 9.34r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 9.80r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 10.13r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 10.69r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 11.16r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 11.82r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 12.06r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 12.42r 0.00u 0.00s 0% 3212k
load: 17.63  cmd: top 61547 [sysctl mem] 12.98r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 13.61r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 14.09r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 14.57r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 15.84r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 18.32r 0.00u 0.00s 0% 3212k
load: 17.34  cmd: top 61547 [sysctl mem] 18.61r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 19.69r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 20.07r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 20.48r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 20.89r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 21.59r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 22.37r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 23.09r 0.00u 0.00s 0% 3212k
load: 16.83  cmd: top 61547 [sysctl mem] 23.82r 0.00u 0.00s 0% 3212k

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to