Skip to content
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

Closed
TaiJuWu opened this issue Sep 21, 2023 · 5 comments · Fixed by apache/nuttx-apps#2085
Closed

qume performance measure #10754

TaiJuWu opened this issue Sep 21, 2023 · 5 comments · Fixed by apache/nuttx-apps#2085

Comments

@TaiJuWu
Copy link
Contributor

TaiJuWu commented Sep 21, 2023

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?

@xiaoxiang781216
Copy link
Contributor

I want to test my code for nuttx. Is it available test on QEMU?

Yes.

I attempted use os perf but pipe2 does not work for qemu-armv8a:nsh_smp Is it resolved?

what' problem?

Or I must measure performance on real hardware?

it's always better to meaure on the real hardware.

The osperf always trigger memory dump and I don't find any documentation about it. Can anyone give me some suggestion?

@Gary-Hobson could you take a look?

@TaiJuWu
Copy link
Contributor Author

TaiJuWu commented Sep 22, 2023

I want to test my code for nuttx. Is it available test on QEMU?

Yes.

I attempted use os perf but pipe2 does not work for qemu-armv8a:nsh_smp Is it resolved?

what' problem?

Or I must measure performance on real hardware?

it's always better to meaure on the real hardware.

The osperf always trigger memory dump and I don't find any documentation about it. Can anyone give me some suggestion?

@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.

@Gary-Hobson
Copy link
Contributor

I want to test my code for nuttx. Is it available test on QEMU?

Yes.

I attempted use os perf but pipe2 does not work for qemu-armv8a:nsh_smp Is it resolved?

what' problem?

Or I must measure performance on real hardware?

it's always better to meaure on the real hardware.

The osperf always trigger memory dump and I don't find any documentation about it. Can anyone give me some suggestion?

@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
I also found that the time you mentioned is incorrect. I am analyzing the reasons now and may have results later.

image

@TaiJuWu
Copy link
Contributor Author

TaiJuWu commented Sep 22, 2023

I want to test my code for nuttx. Is it available test on QEMU?

Yes.

I attempted use os perf but pipe2 does not work for qemu-armv8a:nsh_smp Is it resolved?

what' problem?

Or I must measure performance on real hardware?

it's always better to meaure on the real hardware.

The osperf always trigger memory dump and I don't find any documentation about it. Can anyone give me some suggestion?

@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 I also found that the time you mentioned is incorrect. I am analyzing the reasons now and may have results later.

image

Thanks a lot.

@Gary-Hobson
Copy link
Contributor

@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.

image

And you need to enable the following configuration

CONFIG_DEBUG_SCHED_INFO=n
CONFIG_PIPES=y
CONFIG_TESTING_OSPERF=y

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants