-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qume performance measure #10754
Comments
Yes.
what' problem?
it's always better to meaure on the real hardware.
@Gary-Hobson could you take a look? |
When I use QEMU to measure performance the time looks incorrect, even only pass 1s on real world but the result shows 14s. So I’m not sure this behavior is available and I have attempted to find the answer but failed. |
There were some issues running on arm64 which I have fixed |
Thanks a lot. |
@TaiJuWu You can use this PR(apache/nuttx-apps#2085) to resolve runtime errors. The time display error is due to the fact that in SMP mode, the time obtained by different CPUs through up_perf_gettime is not synchronized, and end may be smaller than start, resulting in time errors. And you need to enable the following configuration
|
I want to test my code performance for nuttx.
Is it available test on QEMU?
I attempted use os perf but pipe2 does not work for qemu-armv8a:nsh_smp
Is it resolved? Or I must measure performance on real hardware?
The osperf always trigger memory dump and I don't find any documentation about it.
Can anyone give me some suggestion?
The text was updated successfully, but these errors were encountered: