-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ZPS][Journeys] Utilize hybrid strategy for ZPS/Journeys integration.
The initial iteration of the "related searches" ZPS/Journeys integration logic (as implemented by crrev.com/c/4090705) was able to successfully overcome some of the flakiness associated with the traditional DOM extraction approach by sourcing "related searches" from prefetched ZPS response data. One consequence of this approach was that the "related searches" annotations provided by the ZPS prefetch logic would often completely overwrite those supplied by the SRP DOM extraction flow. Based on feedback from others, it turned out that the SRP-derived "related searches", which were now being overwritten by the integration logic, were often qualitatively better than those provided by the ZPS prefetch flow. After some further discussion, it was determined that the ideal approach would be to augment (rather than overwrite) the set of SRP-derived "related searches" using data obtained via the ZPS prefetching infra. As such, this CL updates the current ZPS/Journeys integration to implement this new strategy, thereby resulting in increased "related searches" coverage in Journeys without having to sacrifice any annotations obtained via DOM extraction on SRP. Furthermore, prior to this CL, the ZPS prefetch flow could attempt to add "related searches" annotations before the relevant visit was added to the history DB. Given the async nature of both history DB updates and ZPS prefetching, this resulted in a potential race condition which could trigger annotation failures due to a missing entry in the history DB. This CL eliminates this race condition by ensuring that the ZPS-derived annotations are only added AFTER any SRP-derived annotations. BEFORE/AFTER screenshots: - Query = "tom cruise": https://drive.google.com/drive/folders/1va_4RP5NGby9ERQx0GjtUtEfh76NOVJ3?resourcekey=0-3MPRDgGnI_nPF3mbvnGzgQ&usp=sharing - Query = "turtle": https://drive.google.com/drive/folders/1rHOIPvub4_qU3EvHA8Cat3dA5I63lfFV?resourcekey=0-F0ljShpwKDFAXC3wPyHv_Q&usp=sharing Bug: 1378776 Change-Id: I7720912d77980215b6489e7d6a0692a570d649e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4764885 Commit-Queue: Khalid Peer <khalidpeer@chromium.org> Reviewed-by: Sophie Chang <sophiechang@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1187829}
- Loading branch information
Khalid Peer
authored and
Chromium LUCI CQ
committed
Aug 24, 2023
1 parent
7757ff2
commit 6183d7f
Showing
8 changed files
with
207 additions
and
104 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.