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

Implement software bus bulk transfer functional test #2379

Closed
jphickey opened this issue Jun 16, 2023 · 0 comments · Fixed by #2380
Closed

Implement software bus bulk transfer functional test #2379

jphickey opened this issue Jun 16, 2023 · 0 comments · Fixed by #2380
Assignees

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Requests have been received to include software bus performance as part of the test matrix.

Describe the solution you'd like
Start by implementing a functional test case (as part of cfe_testcase) that emulates using the software bus for bulk message transfer, by sending a fixed large number of messages (e.g. 1 million). This process can be timed, and this in turn will give some indication of relative performance of the implementation.

Additional context
This obviously could be much more sophisticated. The proposed test only covers the simplest case, in single thread/single core context, and the results are only comparable to successive runs on the exact same hardware with the same compiler and same compiler flags. Nonetheless, monitoring the result before and after a change will provide at least one simple metric of whether that change affects performance or not.

A follow-on change should perform a similar test with multiple threads, and thus give some metrics to how well SB scales across cores.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Jun 16, 2023
jphickey added a commit to jphickey/cFE that referenced this issue Jun 16, 2023
Add a functional test that moves a large number of messages across the
bus as fast as possible (i.e. with no delay).  The process is timed, thus
offering some metric as to the single thread/single core performance of
the software bus implementation underneath.

Note that due to vast differences between hardware, results should only
be compared between successive runs on the exact same hardware, such as
before and after a change was made.
dzbaker added a commit that referenced this issue Sep 1, 2023
@dzbaker dzbaker closed this as completed in 8753a09 Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants