Predictable Processor Performance

[Whistler]

@stpn

It looks like the 15% utilization is /.fly/hallpass, which seems out of my control? I am not sure if I am reading the situation correctly. I could not find much more information about what hallpass does, so any pointers would be helpful.

and if Fly wish to expand on hallpass’ behaviour, please see also:

256MB Machine OOM & Fly's hallpass daemon

With recent 256MB Machine Out Of Memory errors, e.g. @PietroPan’s here & @vrnithinkumar’s here, I have been wondering if the one item in a Fly VM that isn’t under an Organization’s control - Fly’s hallpass daemon (inserted at runtime?) - may have recently been updated? If this is the case(?), is it possible that Fly’s hallpass is now pushing some 256MB Machines - those that have previously been operating close to but not OOM - into OOM errors? fly ssh console -C "sh -c 'date;uptime;ps -aux | g…

alas, the “topic was automatically closed 7 days after the last reply. New replies are no longer allowed”

hallpass is highest % memory in top on a 256MB Machine:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
322 root 20 0 1241920 37308 0 S 0.0 17.1 3:21.29 hallpass

uname -a:
Linux 9185937b161d83 5.15.98-fly #g534f603e72 SMP Fri Aug 9 18:17:05 UTC 2024 x86_64 GNU/Linux