Moved toke log to it's own DB collection w/ cached statistics. Tokebot statistics page-load time decreased by up to 20-30x: a1b602efdb
Moved toke log to it's own DB collection w/ cached statistics. Tokebot statistics page-load time decreased by up to 20-30x: a1b602efdb
Once toke logs are migrated to a dedicated portion of the DB, and tokebot profile pulls off of a minimized tokemap from the stats DB, we should consider caching certain server-side stats in RAM…
We should wait until #186 is solved, as DB-side toke handling is probably going to change soon.
Refactored userSchema.statics.findProfile()'s tokebot profile generation procedure: 42ad17072f
Looks like the tokebot part of userSchema.statics.findProfile needed tuning.
Calculating the tokemap wasn't the issue, and actually seems to be just as fast, if not faster, than pulling a map…