4 ms·
I don't want my browser on my phone to require a gb of memory thank you very much. It's bad enough that desktop browsers like chrome are complete memory hogs w
by stephenr 12y ago
I don't want my browser on my phone to require a gb of memory thank you very much.
It's bad enough that desktop browsers like chrome are complete memory hogs without stuff like this, I hate to imagine what a phone browser would be like if "fuck it, modern phones have heaps of resources" was the approach to all decisions.
Next you'll be suggesting a compression algorithm that only works anywhere near realtime when it has 8x1ghz+ cores to spread the work over.
- DiabloD3 12y agoYour phone won't require it. It will temporarily use slightly more memory (12MB is very little on modern Android phones), and it would decrease the time required to render the page (due to less CPU power required to compress then decompress over gzip -1).
- stephenr 12y agoMy concern is with your general concept of: > Memory usage isn't that big of a concern anymore
- tandemstrong 12y agoWell, it will use much less than that. The real "memory cost" of decompression will be : + compressed size and that's it. Decompression doesn't use any memory, only the I/O buffers. On the compression side, the memory cost is : + buffer for compression (typically == size of data to compress) + 16 KB for tables And that's it. We are very very far from the 12 MB mentioned.