Server stuff for Yog...possibly

I do not know if this is of any use to you, but I did discover this today:

http://getsatisfaction.com/mojang/topics/smp_server_memory_leak

Stated issue was:
Leak in latest SMP Server -- When leaving a server running over night (no players connected) the server executable will eventually consume well over a gig of memory and become a CPU hog. I've reproduced this quite reliably each time on fresh worlds. Though a simple solution is to just restart the server; any progress made earlier isn't saved.


Resolution:
You can mitigate the memory growth problem by flushing blocks to disk periodically with save-all. I like hMod's SaveReloadPlugin. Minecraft does not reliably sync to disk.

Also here are some garbage collection/memory settings for the JVM, including a setting to cap the maximum garbage collection time. Criticisms welcome.

java -server -Xmn512M -Xms1024M -Xmx2500M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:+UseAdaptiveGCBoundary -XX:MaxGCPauseMillis=500 -XX:-UseGCOverheadLimit -XX:SurvivorRatio=16 -Xnoclassgc -XX:UseSSE=3 -XX:ParallelGCThreads=3 -jar minecraft_mod.jar nogui

This isn't really a script, it's just a bunch of extra arguments to the java command that starts up the server jar file. This will tell the JVM to do some specific stuff ( mostly related to garbage collection ), which does actually seem to help lag/performance as well.

I do not know if this is at ALL helpful, but just trying to assist in some small way.

Mm... I just realized now we don't do periodical save-all, as I don't know how to execute server commands with Bukkit. Maybe doing it manually would fix it.

CraktBukkit is being a bit touch-and-go about it's server commands, I'm sure if it even comes down to it, just work out a time that there is noone on and a quick save-all and restart manually every now and then :3