You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run into some system-wide perf_events buffer limitations when many halo-enabled processes are running at once. See the comment here: halo-project/llvm@e389423
We had to change the noop test to not spawn 50 clients on the same system because of a pretty low default kernel limit on the number of pages that can be used for perf_events buffers. Now that we have to create one buffer per core, it's quite possible to hit this limit without some care.
One way around this problem would be to only gather sampling data from some CPUs and/or reduce the number of pages in the ring buffer. We can also find out how to increase /proc/sys/kernel/perf_event_mlock_kb and tell users to follow those instructions.
The text was updated successfully, but these errors were encountered:
We run into some system-wide perf_events buffer limitations when many halo-enabled processes are running at once. See the comment here: halo-project/llvm@e389423
We had to change the
noop
test to not spawn 50 clients on the same system because of a pretty low default kernel limit on the number of pages that can be used for perf_events buffers. Now that we have to create one buffer per core, it's quite possible to hit this limit without some care.One way around this problem would be to only gather sampling data from some CPUs and/or reduce the number of pages in the ring buffer. We can also find out how to increase
/proc/sys/kernel/perf_event_mlock_kb
and tell users to follow those instructions.The text was updated successfully, but these errors were encountered: