At the moment PrivateMessageManager which handles loading, creating and deleting private messages on database level does not have any type of caching, this could potentially overload the database and should be high priority.
This can be easily achieved as we don't really need to "update" the cache and only add and remove things. Pretty straight forward.
At the moment PrivateMessageManager which handles loading, creating and deleting private messages on database level does not have any type of caching, this could potentially overload the database and should be high priority.
This can be easily achieved as we don't really need to "update" the cache and only add and remove things. Pretty straight forward.