[Greasemonkey] Mark my links: an E4X example

[Jeremy Dunck]

On 3/1/06, Johan Sundström <oyasumi at gmail.com> wrote:
>
> > /me adds yet another tick next to "need to make val storage scalable".
>
> Ah. When do I hit the roof? I was considering whether to split it into
> lots of different values rather than the big JSONish gob of data, but
> didn't come up with any compelling reason to. What bounds are there on
> storage, and does splitting it up into different values help?
>

Actually, fewer values are better.   All values are loaded into memory
at FF startup, currently.  Nik showed that memory usage climbs
quickly, and that somewhere around 10,000 values, FF starts having
issues.

I think up to about 500 would not be particularly noticable (other
than mem usage).

... the comparison is in the list archive, but I'm off for an exam. 
I'll try to dig it up after that.