News for hackers. Stuff that matters.

nnk

That expiring triggers could be somehow useful. But in most cases it's not worth to query memcached from database (selects). The reason is it's much faster to query memcached directly without even opening database connection.

All these caching things make applications complex, because cache invalidation it's a complex task.

MySQL is doing right steps - it's doing caching itself via InnoDB buffer pool. And makes the interface faster by replacing SQL queries with fast memcached API.

What you've described it's MySQL query cache.

MySQL memcached is a memcached deamon that uses InnoDB storage instead of in-memory storage. The caching is done by InnoDB itself.

(and actually it's possible to enable the optional in-memory storage too)

http://dev.mysql.com/doc/refman/5.6/en/innodb-memcached.html

Is there an example of posgtres nosql doing like 700K requests/sec?
> Just what App Engine already offers

No, it doesn't.

"The Memcache Python API High performance scalable web applications often use a distributed in-memory data cache in front of or in place of robust persistent storage for some tasks"

MySQL memcached is not a cache, it's a persistent storage with memcached API. And it's fast.

pgmemcache is a memcached client, it connects to external memcached server. Which is, um, quite useless.
Does it support range scan selects (example: "where f > 5") as HandlerSocket do?
Re:Diablo III open beta this weekend on Friday April 20, 2012 @12:45PM (#3868661)
Even if you don't have any battle.net account, you can create a new one and play the beta.