https://bugs.kde.org/show_bug.cgi?id=388545
--- Comment #3 from Alex <ene...@gmail.com> --- Created attachment 109691 --> https://bugs.kde.org/attachment.cgi?id=109691&action=edit Natron simple resize node setup I've done little research regarding this and tested ImageMagick, GMIC, PS and Natron. I was using this photo to test: https://static.pexels.com/photos/770526/pexels-photo-770526.jpeg IM: convert test.jpg -filter Cubic -resize 300% out.jpg GMIC: gmic test.jpg -resize 300%,300%,100%,100%,5 output out.jpg PS: open and resize 300% Natron: Read node -> Resize node with scale 3 and cubic filter -> Viewer node, GPU rendering disabled and display clip disabled and zoomed to 100% IM indeed is using only 1 cpu and it takes about 23 seconds. GMIC seems to use all cpus and it takes about 9 seconds with cubic and 2 seconds with nearest-neighbor interpolation (just -resize 300%,300% in command line) PS: about 3 seconds with cubic interpolation and... Natron: about 2 seconds with 8 threads set and about 5 seconds with 1 thread set inside options so it's both really, really fast and multi-threaded. I couldn't test Krita as it limits image resize to 10000px, but maybe some code from Natron can be used: https://github.com/MrKepzie/Natron I couldn't find resize node specific code though... -- You are receiving this mail because: You are watching all bug changes.
