SuperKenVery
SuperKenVery
@oconnorir Thanks for the link, but I don’t think it solves our problem because what we are lacking is the memory bandwidth information…
> About the i/o bandwidth changes. I don’t think they belong in here. The focus on asitop was entirely on the SoC and IMO, I think it should stay that...
Well, that’s a little problem. I changed os.rmfile to subprocess.Popen(“sudo rm …”) so that you can run asitop without sudo. This makes debugging easier. But I don’t think it means...
I have a genius (stupid) idea. Can we use the powermetrics binary from macOS 12 directly on macOS 13? Are all the system calls still there?
> > Well, that’s a little problem. I changed os.rmfile to subprocess.Popen(“sudo rm …”) so that you can run asitop without sudo. This makes debugging easier. But I don’t think...
> asitop often shows the “Package Power” being lower than CPU Power. This never happened to me. The code for `package power` is at file parsers.py line 128. Maybe you...
Wow! I think we can let asitop download that thing automatically. macOS 12 won’t change anymore, so powermetrics would be in a fixed position in the recovery image I guess....
Well, most importantly, are memory bandwidths available?
> The license isn't compatible and it can’t be hosted on GitHub. Yeah but I think it's ok to download it from apple. We can write the script to download...
Yeah powermetrics runs but doesn’t report memory bandwidth anymore, at least on my machine. One of our ideas is to run macOS 12’s powermetrics on macOS 13 but I haven’t...