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

perf: Gatling benchmarks #1978

Merged
merged 164 commits into from
Mar 24, 2025
Merged

perf: Gatling benchmarks #1978

merged 164 commits into from
Mar 24, 2025

Conversation

MichaelsJP
Copy link
Member

Pull Request Checklist

  • 1. I have rebased the latest version of the main branch into my feature branch and all conflicts
    have been resolved.
  • 2. I have added information about the change/addition to functionality to the CHANGELOG.md file under the
    [Unreleased] heading.
  • 3. I have documented my code using JDocs tags.
  • 4. I have removed unnecessary commented out code, imports and System.out.println statements.
  • 5. I have written JUnit tests for any new methods/classes and ensured that they pass.
  • 6. I have created API tests for any new functionality exposed to the API.
  • 7. If changes/additions are made to the ors-config.json file, I have added these to the ors config documentation
    along with a short description of what it is for, and documented this in the Pull Request (below).
  • 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
  • 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
  • 10. For new features or changes involving building of graphs, I have tested on a larger dataset
    (at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
  • 11. For new features or changes involving the graphbuilding process (i.e. changing encoders, updating the
    importer etc.), I have generated longer distance routes for the affected profiles with different options
    (avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
    points generated from the current live ORS.
    If there are differences then the reasoning for these MUST be documented in the pull request.
  • 12. I have written in the Pull Request information about the changes made including their intended usage
    and why the change was needed.
  • 13. For changes touching the API documentation, I have tested that the API playground renders correctly.

Fixes # .

Information about the changes

  • Key functionality added:
  • Reason for change:

Examples and reasons for differences between live ORS routes, and those generated from this pull request

Required changes to ors config (if applicable)

Sorry, something went wrong.

@github-actions github-actions bot added the test label Mar 10, 2025
@MichaelsJP MichaelsJP force-pushed the test/gatling-benchmark-rebase branch 2 times, most recently from 9b8e1a2 to d81ab5d Compare March 10, 2025 09:57
@MichaelsJP MichaelsJP changed the title test: gatling benchmark rebase test: gatling benchmark Mar 10, 2025
@github-actions github-actions bot added test and removed test labels Mar 10, 2025
@MichaelsJP MichaelsJP requested a review from takb March 10, 2025 09:58
@github-actions github-actions bot added test and removed test labels Mar 10, 2025
@MichaelsJP MichaelsJP force-pushed the test/gatling-benchmark-rebase branch from 3791915 to f15b218 Compare March 10, 2025 10:56
@MichaelsJP MichaelsJP force-pushed the test/gatling-benchmark-rebase branch from a892484 to 7219f30 Compare March 19, 2025 09:02
@MichaelsJP MichaelsJP force-pushed the test/gatling-benchmark-rebase branch from 1568545 to eaefbfa Compare March 19, 2025 10:12
@MichaelsJP MichaelsJP marked this pull request as ready for review March 19, 2025 14:55
@github-actions github-actions bot added test and removed test labels Mar 19, 2025
@MichaelsJP MichaelsJP changed the title test: gatling benchmark perf: gatling benchmark Mar 19, 2025
@MichaelsJP MichaelsJP changed the title perf: gatling benchmark perf: Gatling benchmarks Mar 19, 2025
@MichaelsJP MichaelsJP force-pushed the test/gatling-benchmark-rebase branch from ece5d40 to 71bf0d0 Compare March 19, 2025 14:57
Copy link
Contributor

@takb takb left a comment

Choose a reason for hiding this comment

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

lgtm

@takb takb merged commit 0a20258 into main Mar 24, 2025
32 checks passed
@takb takb deleted the test/gatling-benchmark-rebase branch March 24, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants