On 6/21/2014 3:56 AM, Rob wrote:
Robert Kaiser <[email protected]> wrote:
Rob schrieb:
The reason why some of the .sqlite files are so darn large is partly
the silly pre-allocation that is done on them.
"Silly" is in the eye of the beholder. The preallocation makes write
access to the DB much faster. It's a tradeoff. The vast majority of
people have local profiles on their computer and their disk space is
huge and cheap, while their time probably isn't.
KaiRo
I would first thoroughly the case where allocating disk space is
so slow that it is better to pre-allocate it before I would hardcode
such big pre-allocation increments in the software. Even then I would
have put a pref in the code that could override the allocation increment
for cases I did not think about.
The people who think "disk space is huge and cheap" clearly have not
considered roaming profiles. I forgive them that they forget about
a specific configuration they don't have on their home system, but not
that they keep holding on to it even after they have been informed about
the negative impact it has on others.
Fortunately Seamonkey has been phased out where I work, so I no longer
have to worry about issues like this. But maybe other people still have.
Disk space, IS huge and cheap these days, however, compared to the speed
of RAM and the CPU, it is rather SLOW. That's why SSDs are becoming
more popular as the price of the chips goes down. I suspect that hard
drives for personal computing will virtually disappear in a couple of years.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
