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

sd_bench: Display maximum time for maximum write time #22860

Merged

Conversation

muramura
Copy link
Contributor

@muramura muramura commented Mar 9, 2024

Solved Problem

Check everything to know the maximum write time max.
I judge a MICRO SD card as good or bad by knowing the max time.

Solution

Show the maximum value of the maximum write time.

Changelog Entry

None

Alternatives

None

Test coverage

None

Context

Screenshot from 2024-03-10 01-20-59

}

cfg->total_blocks_written = total_blocks;
PX4_INFO(" Avg : %8.2lf KB/s", (double)block_size * total_blocks / total_elapsed / 1024.);
PX4_INFO(" maxMWT: %8i ms", max_max_write_time);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this more readable, even if it breaks alignment:

Suggested change
PX4_INFO(" maxMWT: %8i ms", max_max_write_time);
PX4_INFO("Overall max write time: %8i ms", max_max_write_time);

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion.
I understand about, better not to omit.
The format has been adjusted to match the columns.
With the columns aligned, I removed the numeric format.

Screenshot from 2024-03-17 21-06-58

@muramura muramura force-pushed the PX4_Display_maximum_time_for_maximum_write_time branch from c568f2f to 630eead Compare March 17, 2024 12:11
@bkueng bkueng merged commit 6385087 into PX4:main Mar 20, 2024
87 of 89 checks passed
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 this pull request may close these issues.

None yet

2 participants