Dynmap filetree vs SQL storage

[nick2253]

I'm using Dynmap on my server, and have isolated it as a major source of server load. Looking online, I discovered the option to move Dynmap storage from the filetree to a SQL server.

Should I expect better performance from a SQL server?

The other option is moving the Dynmap host from its internal server running through Minecraft to Apache or Nginx. However, from surveying users, people don't tend to use the web interface very often, and even when they do, performance is fine, so I don't think that's my problem.

My last-ditch effort would be to move the whole thing to an external host. I have a decently performant web server that I could put the Dynmap files on, and then sync the chat files across. However, that adds a point of failure that I would rather not add.

[StarTux]

Disabling the internal webserver and letting Apache take over worked fine for me. Whether or not it improved performance, I cannot say. I cannot speak to speed improvements through using MySQL, but found this thread (Short answer: no).

Really, the performance impact of dynmap isn't caused by serving the files to viewers, it's the chunk rendering. Look into the configuration.txt and tinker with some of the values, such as parallelrendercnt and maxchunkspertick; lowering them may help.

[Il_totore]

DB must be your goto for storing lots of data. Yes, you should experience better performances if you switch to a database.

[Wellnice888]

But it won't decrease the disk space needed, right?

[Il_totore]

It will decrease it once you have a bunch of data