plotly / plotly/Kaleido

resolve stability / performance issues related to GPUs

Open
#341 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 performance
Dominant language
Python
Stars
498
Forks
62
Avg merge
1d 11h
Merged PRs (30d)
2

Description

If Kaleido runs with GPU enabled on a CI system that doesn't have a GPU it can fail catastrophically. We believe this is because of changes in Chromium, but the net result is that (for example) rendering all the plotly.js test images takes about twice as long as it used to with Kaleido 1.0.0rc15.

possibly related to #323 ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the GPU-enabled failure on a CI system without a GPU and measure plotly.js test-image rendering against Kaleido 1.0.0rc15. Review the possible relationship to issue #323 and the reported Chromium changes. Done means non-GPU CI no longer fails catastrophically and the rendering performance regression is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
ci-cd, performance, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.