Yandex ‘leak’ reveals 1,922 search ranking factors

Re:Yandex ‘leak’ reveals 1,922 search ranking factors by ethbr0 on Monday January 30, 2023 @11:35AM (#34582191)

Also, I'd assume it's highly time-agnostic (i.e. content change timespan : compute availability timespan).

So you can run your bulk-recomputing whenever you have spare capacity.

Stale rankings aren't great, but don't hurt that much. As long as your liveness is more frequently updated, so you don't send people to dead sites.

[ Parent | on HN ]

Re:Yandex ‘leak’ reveals 1,922 search ranking factors by h0l0cube on Monday January 30, 2023 @06:26PM (#34588199)

Certainly caching is important, especially for Word2Vec or other NLP which you'd want to happen in a separate stage after crawl, but as someone mentioned in a sibling comment, there are some factors that are calculated per-query, which can have a lot of cache misses for novel queries.

[ Parent | on HN ]

Re:Yandex ‘leak’ reveals 1,922 search ranking factors by ethbr0 on Monday January 30, 2023 @09:06PM (#34589957)

If so, I'd highly suspect Google varies the compute/cache permitted for novel queries.

By this point, I can't imagine they haven't automatically balanced {revenueFromQuery} to {costOfQuery}.

No sense delivering hyperoptimized results if you lose money on generating them.

[ Parent | on HN ]

Re:Yandex ‘leak’ reveals 1,922 search ranking factors by h0l0cube on Monday January 30, 2023 @10:08PM (#34590356)

I’d suspect you’re right

[ Parent | on HN ]