Home > Net > C # to tackle the problem of article 5000 of the JSON bosses to guide it
C # to tackle the problem of article 5000 of the JSON bosses to guide it
Time:10-05
This project can't use the multithreading (unity WEBGL, WEBGL support multithreaded), 0.2 seconds to refresh data at a time, three public a set of data objects, that is each update 15000 data, this how to optimize. The bosses have better method
CodePudding user response:
More than 1 w data, people do not see out, use data paging read less as far as possible
CodePudding user response:
0.2 seconds 15000 data.. Come, and the data? The socket or HTTP? What kind of program?
CodePudding user response:
Three items public a data, the game?
So my question is, are you all these 15 k data needs to be saved? Should not need to, is webgl, is showing, outdated data is out of date,
So I say so, you really have a limitation or the data of the 5000 article, this can MVVM, anyway, is always the article 5000, the updated refresh the 5000 refresh data as a also not is what big things, the key is to take 0.2 seconds, 0.2 seconds also does not need to refresh,
Basic is, after all, 200 milliseconds was too fast, "blink", so, I must need "blink" data? No, even a fry a software, the whole great China's hundreds of millions of people in the operation of the data, he will be in normal operation interface for 200 seconds brush a UI, you should brush, so also meaningless,
CodePudding user response:
In fact if analogy for fry a software, the operation of the stock exchange to set one hundred million, then cleaning, synthesis, and give you
So if that's the case, he will do in the outside, to your UI operation is actually very few
So now, will have the spark, storm, flink the value of such things exist, these things outside in the batch batch give you wash good, good synthesis, to the front end is just a small number of tasks