Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Add performance tests #7443

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

Open
archmoj wants to merge 46 commits into master
base: master
Choose a base branch
Loading
from performance-tests
Open

Add performance tests #7443

archmoj wants to merge 46 commits into master from performance-tests

Conversation

@archmoj
Copy link
Contributor

@archmoj archmoj commented Jun 17, 2025 •
edited
Loading

To run all the tests for various traces please run:

npm run test-performance
  • scatter (modes: markers, lines & markers+lines)
  • scattergl (modes: markers, lines & markers+lines)
  • scattergeo (modes: markers, lines & markers+lines)
  • bar (modes: group, stack, overlay)
  • histogram (modes: group, stack, overlay)
  • box (modes: show/hide points)
  • violin (modes: show/hide points)
  • contour
  • heatmap
  • image

Copy link
Contributor

I think we can skip benchmarking of pie charts - nobody could make sense of a 1000-item pie chart, so behavior at scale isn't a concern.
alexcjohnson reacted with laugh emoji

@gvwilson gvwilson added feature something new P1 needed for current cycle infrastructure build process etc. performance something is slow labels Jun 20, 2025
archmoj added 20 commits June 20, 2025 09:58
Copy link
Contributor Author

archmoj commented Jun 24, 2025

@gvwilson Please find the example output file generated locally:
all.csv
Thank you.

Copy link
Contributor Author

archmoj commented Jun 27, 2025 •
edited
Loading

@gvwilson with previous improvements, each test case is isolated and run inside a fresh window.
The browser is no longer encountered crash on CI (as well as locally).
Here you could find example results: https://app.circleci.com/pipelines/github/plotly/plotly.js/12132/workflows/d9e39715-6d98-48c4-b34c-26d2baf9e57a/jobs/268411/artifacts

Now with this more stable setup we would be able to further increase the number of data points i.e. to test the failing scenarios.

Copy link
Contributor Author

archmoj commented Jun 27, 2025

@gvwilson Now the test results also include the failing cases in both all.csv and failed.csv files.
https://app.circleci.com/pipelines/github/plotly/plotly.js/12142/workflows/98ecc56e-d3f6-4f5d-aff1-723879408090/jobs/268665/artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

feature something new infrastructure build process etc. P1 needed for current cycle performance something is slow

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /