Saving too many players data causes problems

[Florke64]

This is very abstract situation, but...

If there was ~10k new players during one plugin's runtime and EVERY ONE OF THEM did a statistic and/or drop config update (generally amended own Player's Data) - by breaking stone, leveling-up or filtering custom drops - and (even more abstract) they will stay on your server (assuming you have that many slots) and there will be somehow auto-save or plugin reload (causing saving unsaved data into database): server can basically have issues uploading that data.

I could potentially make it better but it will require making separate methods for different "database save types" - it will then cause additional effort to maintain everything correctly if database inserting code need updating...