4 ms·
Oh I see what you're saying now...to my knowledge we never had a feature like that, unfortunately I think it would be fairly expensive to implement the way our
by wanderr 13y ago
Oh I see what you're saying now...to my knowledge we never had a feature like that, unfortunately I think it would be fairly expensive to implement the way our data is structured right now (it's optimized for looking up playlist -> songs not the other way around), but I can definitely see the appeal of a feature like that. I could see us precomputing a list of playlists to check out per song and applying some quality metrics to them...precomputing would preclude us from being able to do looking up playlists by multiple songs. Anyway I will mention it to my boss, can't make any promises of course.
- d0m 13y agoTalking about the way Grooveshark structure their data could be an interesting topic. I would be surprised to test how much time it would take to find some playlists containing a song even with a trivial algorithm. The reason I'm saying that is that it would be very fast for popular songs to find a few playlists (We don't need 1000 results, just a few is great for our case). And for the less known songs, I'm happy to wait for quality playlists! ;)