3 ms·
Just had a thought. If I generate 8MB PNG files with noise in them and upload 1000 of such files, your servers will choke. Maybe you should charge per MB.
by rorrr2 13y ago
Just had a thought. If I generate 8MB PNG files with noise in them and upload 1000 of such files, your servers will choke.
Maybe you should charge per MB.
- kraken-io 13y agoYou are right, our optimization workers will have a lot of work to do to optimize those images. In that case we recommend the use of "callback_url" option to eliminate the possibility of a request timeout.
- rorrr2 13y agoNo, I mean it can be used to DoS you. Give it a try. Optimizing even one 8MB noise PNG is a huge amount of CPU work.
- IanCal 13y agoI've just tried compressing a 12 meg png file with pngcrush locally (generated with `convert -size 1000x2000 xc: +noise Random noise.png`, it only took a few seconds and didn't tax the processor much. Maybe pngcrush handles it better than other things but that didn't seem onerous.
- kamkha 13y agoI would guess that the service does something more along the lines of `pngcrush -brute` which is significantly more taxing.