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

Add three benchmarks for the framework #32

Merged
merged 1 commit into from
Jun 19, 2020
Merged

Add three benchmarks for the framework #32

merged 1 commit into from
Jun 19, 2020

Conversation

twilker
Copy link
Contributor

@twilker twilker commented Jun 19, 2020

For such a framework benchmarks are quite important. For that I added three benchmarks:

  • Real World benchmark: editing 400 out of 2000 files
  • Worst case scenario: Sequential execution (to measure the overhead based on total time executing one work unit)
  • Base case scenario: 2000 randomized parallel executable workloads.

Optimize performance by removing unnecessary code.
There was a spinning thread which queued the messages. I am not sure why it was there. The only advantage of that is when it is important that messages are publish in the same order they are given to the message board. But that is no real scenario.

This resolves #21

Optimize performance by removing unnecessary code.
@twilker twilker added the documentation Improvements or additions to documentation label Jun 19, 2020
@twilker twilker added this to the 2020.6 Release milestone Jun 19, 2020
@twilker twilker merged commit cd38f83 into master Jun 19, 2020
@twilker twilker deleted the benchmarks branch June 19, 2020 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create benchmarks
1 participant