Skip to content

Comment on The SeatGeek Event Recommendations APIparent

Comments

It can be done fast enough. There is some pre-processing of the raw data at startup time, so all we store in memory is a matrix representation of our user/artist preference graph.

A typical preference calculation for a new arbitrary set of artists takes 50-100ms, at which point it is cached for a while. Our most common queries [individual performers, for example] tend to read from cache, which helps.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.