Re: [aerogear-dev] [simplepush] Performance

On 2013/9/19 5:18 AM, Lucas Holmquist wrote: Hardly. It's just a question of what the right tool for a given job is. (I'll note that Google is spending quite a bit of time and effort improving Maria because they use a LOT of relational DBs for very large data. In this case, however, it's pretty easy to reduce things to simple key/value. I picked Memcache, partly because of the fact that it does record auto-expiration, which means that I don't have to do garbage collection on uncollected records. If you switched to an alternate schema (such as keeping a single record per UAID that contained all the CHID data as well as stuff like the proprietary info or other crap), you could even use simple flat files and skip the DB requirement altogether. We were kicking the idea around of only storing undeliverable data into the DB, and instead letting each websock connector deal with managing it's own data. For our implementation, I've already preferenced delivery over storage for connected clients and seen a fair bit of improvement on delivery. (Remember, SimplePush is not a 100% guaranteed delivery system, so please avoid using it for nuclear reactor management or pacemakers.) We'll probably hold off on doing further memory refinement until we get some actual use data, but I like having options available.