|
|
|
|
|
by lysecret
1528 days ago
|
|
Interesting post. On thing to note, this seems to be about "on request" ranking. E.g. googleing something and in 500ms you need the recommended content. However, a lot of usecases are time insensitive rankings. Like recommending content on netflix, spotify etc. (spotifys discover weekly even has a one week! request time :D). In which case you can just run your ranking and store the recs in your DB and its much much easier. |
|