7 ms·
Do you also include the library to render a jpeg? And maybe the whole OS required to display it on your screen? There are very many uses where any fixed overhe
by Gigachad 4y ago
Do you also include the library to render a jpeg? And maybe the whole OS required to display it on your screen?
There are very many uses where any fixed overhead is meaningless. Imagine archiving billions of images for long term storage. The 4GB model quickly becomes meaningless.
- stavros 4y ago> Do you also include the library to render a jpeg? And maybe the whole OS required to display it on your screen? No, what does that have to do with reconstructing the original data? If the fixed overhead works for you, that's fine, but including it is not meaningless.
- 112233 4y agoFixed overheads are never meaningless. O(n^2) algorithm that processes your data in 5s is faster on your data than O(log n) that takes 20 hours. Long term storage of billions of images is meaningless, if it takes billions of years to archive these images.
- Gigachad 4y agoIt’s a one time cost rather than per image. You need the 4GB model only once and then you can uncompress unlimited images.
- 112233 4y agoYes, but each image needs access to this 4GB (actually, I have no idea how much RAM it takes up), plus whatever the working set size is. It is a non-trivial overhead that really limits throughput of your system, so you can process less images in parallel, so compressing billion of images in reasonable time suddenly may cost much more than the amount of storage it would save, compared to other methods.