I wonder if it is possible to track running tasks and show which one is using up what amount of ram/cpu.
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
Unlike the old AmigaOS <= 3.9 one the AmigaOS 4.x ExecNG task scheduler does record the CPU usage times of the executed tasks. I don't know if tools like SysMon, Scout, etc., can display it, but I implemented a "top" like, shell-only tool several years ago which did. IIRC I never did a public release of it and it was only available on the internal OS4 developer/beta-tester FTP server, but in the unlikely case it's still working (very likely doesn't work with beta multi-core kernels) it's OK to upload it to os4depot.net if one of the former OS4 developers or beta testers still has it.
It would be awesome to get this kind of information into existing GUI based tools/duckies
Thank you
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
I have been wondering for years why there is no tool to display cpu usage of each task and then it turns out that there's been one out all the time (i think i got my first os4 machine in 2008)
I may still have the sources in some old backups, but nothing I can access currently. You can release it if you want, but if it's working the way I think it did it it could be that it requires internal exec includes not part of public SDKs (struct ETask).
I found several different top.lha in the OS4 beta mailinglist in my Thunderbird backups between 2006 and 2008, but even if they have the same name, and as Niels wrote no version strings, they may work completely different. At least the oldest versions couldn't use the CPUs usage timer from ExecNG in struct ETask yet, it was an ugly hack using interrupts instead...