Figure is a major increases in memory in the code, other have ruled out;
Figure 2 is at the start of the run, memory size, ensure that no other factors during the test;
Figure 3 run about a minute, the added value of memory (MB), it is the function of use during loading pointCollection of mass points, every 100 ms draw five points on the map



CodePudding user response:
Understanding the asynchronous loadingCodePudding user response:
Have tried it on asynchronous loading yesterday, is still the same result, memory is on the riseCodePudding user response:
Massive high concurrencyThen find a temporary storage
And then set a timer to data loading step by step
The thinking of similar paging query
CodePudding user response:
Has step by step loading example, or don't understand how to use the