Note. I'm really interested in the sizes of the "large" arrays that work for other people. This is not the first time I have thought about this and welcome feedback.
The scheme, which I will describe in detail below, requires efforts to develop this goal, so it’s better to know if I need to use bandwidth and abandon this idea, or is this a practical method for limiting the maximum bandwidth. In other cases, for others who may be interested, or for my future projects, the gain may be greater.
Usually, when I come across a situation where a large javascript dataset is an option, there are usually other options, and I prefer other options. I'm really not sure what qualifies as big or too big.
I am wondering what works safely in production. I know that there are theoretical limitations, but I cannot find anything within practical limits. As I will describe in detail below, my array has a size of 14,000 elements and 356 thousand. Size.
I understand, of course, that javascript is the client side and depends on the characteristics of the client machine, my code, and to some extent the browser version (in cases where the corresponding internal performance has improved between versions).
Like any reputable modern website, it will also have a mobile version, and, frankly, where there are memory problems.
, , , , (, , , N ).
: 32- , , .
:
.
, . , , . , .
14 000 356 . (216 . ), 20% (2 , 65 ). .
['s=h07225','s=h0430','s=h0853','m=sm:th8804']
- , .