4 ms·
>all done in 50ms of compute time for resizing I would be doubtful I don’t know the details of your environment or timing precision, but I’m quite sure that a
by trevyn 9y ago
>all done in 50ms of compute time for resizing I would be doubtful
I don’t know the details of your environment or timing precision, but I’m quite sure that a single core on a modern server CPU can resize and JPEG compress more than 20 reasonably-sized images per second. :-)
- sitepodmatt 9y agoYou're probably right, presumably the 50ms of compute time, is that of reasonable 1.6ghz xeon+, and compute time is accounted as actual real compute time - not inclusive of waiting on some virtual CPU to be multiplexed onto a real core.
- ht85 9y agoI benchmarked various programs to resize images a year ago. There was a JS package with native bindings to GD, a go program, and a pure JS implementation. Both go and GD were an order of magnitude faster at scaling down and converting PNG to JPG.