On Jun 28, 2:37 am, Dustin <[email protected]> wrote: > IMO, it's most useful for *very* specific applications where you > have a small number of very popular items that don't change very > frequently. Many applications have a hugely disproportionately hot > object such as one that appears on every page for every user. > Typically, that goes to a single server and that server ends up > saturated.
Yes, this makes sense. Unfortunately for my current app we don't have this kind of data, but I could have used this in the past! Any place where you can accept inconsistencies in often requested data would be a great candidate to put in this L1 cache. Looking forward to the first release labeled 'stable'. If I have time, I'll try to use it in our staging environment as well.
