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

Investigate and Fix Performance Bottlenecks #18

Open
4 tasks
Hoshiningen opened this issue Apr 25, 2020 · 0 comments
Open
4 tasks

Investigate and Fix Performance Bottlenecks #18

Hoshiningen opened this issue Apr 25, 2020 · 0 comments
Labels
performance It's running to slow, or using too much memory

Comments

@Hoshiningen
Copy link
Owner

There are portions of the algorithm that run slow as the size of the image increases. It gets to the point were at reasonably large images (100px by 100px, or so) that the performance becomes unbearably slow.

Investigate the less performant portions of the algorithm and develop solutions to address those issues.

Acceptance Criteria

  • The performance bottlenecks have been found
  • A solution to address them has been decided on
  • The solution has been implemented, and metrics have been recorded to compare against the less performant version
  • A noticeable difference is measurable. The processing times are reasonably quick for the expected-size images (300px by 300px max)
@Hoshiningen Hoshiningen added the performance It's running to slow, or using too much memory label Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance It's running to slow, or using too much memory
Projects
None yet
Development

No branches or pull requests

1 participant