Consider caching subscriptions table in-memory

[davidben]

Or maybe caching them based on classes that are used so we don't have to care about people with huge piles of useless subs (ahem). The prepare query is in the critical path to delivering a message, so it's pretty important.

Might also be worth caching the last N messages in memory for reasonably large N so that that isn't slow. I dunno.