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

Optimize memory consumption of ResizeProcessor #642

Closed
antonfirsov opened this issue Jun 28, 2018 · 1 comment · Fixed by #888
Closed

Optimize memory consumption of ResizeProcessor #642

antonfirsov opened this issue Jun 28, 2018 · 1 comment · Fixed by #888

Comments

@antonfirsov
Copy link
Member

@antonfirsov antonfirsov commented Jun 28, 2018

Currently we are using O(NewWidth * SourceHeight) memory for doing resize operations, however it's possible to do it consuming only O(NewWidth * KernelDiameter) memory, without significant negative effect on speed.

We need to implement a "sliding window" algorithm for this.

It will most likely fix issues like #597.

UPDATE
The issue is now part of the epic #733.

UPDATE 2
The ideas in #733 are abandoned now, we need to implement this with the current architecture.

@JimBobSquarePants
Copy link
Member

@JimBobSquarePants JimBobSquarePants commented Aug 4, 2018

@antonfirsov I'm assigning this one to you for now since you're more likely to get it right than me. Hoping someone from the community will step up though and give us a breather.

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

Successfully merging a pull request may close this issue.

2 participants