I'am not talking about the time to load the scripts, but to run them. Try it yourself - download the app and measure the time from starting it until you can select a graph. This time is constant and way larger than the time to finally load the data.
I'am not talking about the time to load the scripts, but to run them. Try it yourself - download the app and measure the time from starting it until you can select a graph. This time is constant and way larger than the time to finally load the data.
Oh I see that we were not talking about the same thing, indeed after a specific X Mb of json file loading time, the json parse and db load has the biggest load time but until then it's not the db deserialize time but the serialized db that takes the biggest time. Never looked at what "X" we are talking about, I think it must be at least bigger than 5Mb to impact more the deserialize time than the download time :)
I'am not talking about the time to load the scripts, but to run them. Try it yourself - download the app and measure the time from starting it until you can select a graph. This time is constant and way larger than the time to finally load the data.
Oh I see that we were not talking about the same thing, indeed after a specific X Mb of json file loading time, the json parse and db load has the biggest load time but until then it's not the db deserialize time but the serialized db that takes the biggest time. Never looked at what "X" we are talking about, I think it must be at least bigger than 5Mb to impact more the deserialize time than the download time :)