Change Details

Currently, in case of a huge number of visits for an origin, this makes the page querying that result crash (when the cache is initially empty, and even with a populated cache, that could take some time). With this diff, instead of iterating over all origin visits, this uses simpler storage api calls to retrieve the most recent visit (and the most recent associated visit status). This also no longer relies on the cache of all visits for that origin. Related to T3905

Currently, in case of a high number of visits for an origin, this makes the page querying the result crash (with an empty cache). Note that even with a populated cache, the current version could take some time to process. The following diff opens a function which uses simpler storage api calls to retrieve the most recent visit from a given point in time (with its most recent associated visit status) instead of filtering all visits of an origin to retrieve the information. Hence no longer relying on the cache of all visits for that origin either. Related to T3905

Currently, in case of a hugehigh number of visits for an origin, this makes the page querying thate result crash (when the cache is initially empty,ith an empty cache). andNote that even with a populated cache, cache, thatthe current version could take some time)e to process. With thisThe following diff, instead of iterating over all origin visits, this uses simpler storage opens a function which uses simpler storage api calls to retrieve the api calls to retrieve the most recent visit (and themost recent visit from a given point in time (with its most recent associated visit status) instead of filtering all visits of an origin to retrieve the information. This also Hence no longer reliesying on the cache of all visits for that origin either. Related to T3905