Caching UUIDs is slow

[JeromSar]

Caching UUIDs is slow and takes up a lot of memory.

This should probably be done through a MySQL-lite DB.

[JeromSar]

I need some feedback for 05e50cf @StevenLawson @WickedGamingUK @Wild1145

[Fyrsta]

This is a good idea. I think moving a lot of data to a MySQL database is something that should be done as well.

[Wild1145]

Migrating to SQL should speed up the accessing of the data. The only possible issue that I thought of is if Mark wants to change anything, it may be harder to do so if there are going to be less configuration files...

[Fyrsta]

@Wild1145 It isn't too hard to access a database and change the variables as needed. Mark can use Sequel Pro, MySQL Workbench, etc. to manage the database.

[Wild1145]

@WickedGamingUK But why would he want to, when there are already incredibly easy to use YAML files. My point is that whatever is stored in SQL should be stuff that nobody will ever want or need to modify manually.

[Fyrsta]

@Wild1145 Really you should have as much information in one place as possible. I guess leaving configuration settings in a YAML file and move everything else to MySQL would be the best way forward.

[Wild1145]

@WickedGamingUK If all that you care about is speeding up the loading of data then yes, storing everything in SQL would be the best. If you want to keep it reasonably easy for Mark to make modifications, or to keep it relativity easy for other servers to be able to use it, you then should only be storing information that you will not be required to edit.

[JeromSar]

This change should avoid having to cache hundreds of player UUIDs at load time. The JDBC driver should keep UUID lookups less RAM intensive and thus this change should increase performance.

[JeromSar]

I need code review and beta testers @WickedGamingUK @Wild1145 @StevenLawson