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.

Sign up for GitHub

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

Jump to bottom

Unify time measure in some implementations #4

Merged
merged 2 commits into from
Feb 23, 2024
Merged

Unify time measure in some implementations #4

merged 2 commits into from
Feb 23, 2024

Conversation

vikman90
Copy link
Owner

These implementations are yielding an unusually inefficient result:

  • C++
  • Go
  • Rust

This is the performance table, supposedly measured in ops/ms:

Implementation Step perf (max) Step perf (avg) Disc. perf (max) Disc. perf (avg)
JavaScript 43.000,00 24.331,97 2.567.812,50 716.081,97
C# 62.594,50 42.403,85 3.908.416,67 709.109,47
PHP 34.500,00 5.113,62 607.800,00 212.727,68
Java 38.000,00 4.605,37 825.000,00 192.100,51
Python 38.000,00 4.605,37 825.000,00 192.100,51
C++ 887,50 240,02 28.859,81 2.450,07
Go 514,29 106,26 20.288,46 1.801,85
Rust 597,22 126,77 24.791,63 1.652,69

@vikman90 vikman90 linked an issue Feb 23, 2024 that may be closed by this pull request
Wrong time measure in some implementations #2
Closed
@vikman90 vikman90 self-assigned this Feb 23, 2024
@vikman90 vikman90 added the bug Something isn't working label Feb 23, 2024
@vikman90 vikman90 merged commit f5d5cbd into master Feb 23, 2024
8 checks passed
@vikman90 vikman90 changed the title Wrong time measure in some implementations Unify time measure in some implementations Feb 23, 2024
@vikman90 vikman90 deleted the fix-timing branch February 23, 2024 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@vikman90 vikman90

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Wrong time measure in some implementations
1 participant
@vikman90