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 …
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 :)
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 :)