I'm running this build on a Forge with all those mods (and about 10 more) on the same server with the same settings as my Bukkit server, and getting equivalent performance (within a few milliseconds per tile). What are the data you see from /dynmap stats?
I've been a long time dynmap user (I requested the topography renderer). But a recent switch from Bukkit to plain MCS has left me kind of reeling. On Bukkit I get about 40ms/tile for rendering. On plain I'm getting 300+ms/tile.
Dynmap 1.4 a2
MinecraftForge v6.6.0.497
MCS 1.4.7
Server is quad core 3.2ghz, 4GB of ram (3.5 to java).
Load average is 1.52 average, all from java. This is 0.1 average when dynmap is not crunching out maps. It actually appears like dynmap might be running the server out of memory. I can allocate more ram to test this theory. Up to perhaps 12GB. Currently it's pushed out into swap by 300MB.
I'm the only one on the server. Mods present are Buildcraft, RP2, and Dynmap, but with a non-modified map except the pre-fill. Map was pre-filled out to 2000 chunks in all directions. I asked dynmap to radius render 300 from the middle.
Speaking of, dynmap's helper text is not showing up on plain. Commands at the console, or in-game only return text when dynmap does something, not when you /dynmap help, or any other command. It just gives the status updates on chunks rendered.
Edit: MCS topped out at 4GB. I'll sort the 64 bit issue. But that doesn't solve the really long render times though.
0
MCS
2013-01-10 16:15:33 [INFO] [Minecraft] Tile Render Statistics:
2013-01-10 16:15:33 [INFO] [Minecraft] world.ct: processed=19, rendered=19, updated=8, transparent=0
2013-01-10 16:15:33 [INFO] [Minecraft] world.flat: processed=92, rendered=92, updated=8, transparent=0
2013-01-10 16:15:33 [INFO] [Minecraft] world.t: processed=1391, rendered=1391, updated=22, transparent=0
2013-01-10 16:15:33 [INFO] [Minecraft] TOTALS: processed=1502, rendered=1502, updated=38, transparent=0
2013-01-10 16:15:33 [INFO] [Minecraft] Triggered update queue size: 16
2013-01-10 16:15:33 [INFO] [Minecraft] Active render jobs: world
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk Loading Statistics:
2013-01-10 16:15:33 [INFO] [Minecraft] Cache hit rate: 83.10%
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk sets: created=1589, attempted=1589
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk: loaded=38579, attempted=64656
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk load times: 20439.55 msec (0.53 msec/chunk)
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk set load times: 175522.55 msec (110.46 msec/set)
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk set delay times: 155083.01 msec (97.60 msec/set)
2013-01-10 16:15:33 [INFO] [Minecraft] Chunk set exceptions: 0
2013-01-10 16:15:33 [INFO] [Minecraft] World tick list processing calls: 0
Running at 140msec. (Actually running good, but server stuttering pretty bad).
Bukkit
16:21:50 [INFO] Tile Render Statistics:
16:21:50 [INFO] world.ct: processed=673, rendered=673, updated=111, transparent=0
16:21:50 [INFO] world.flat: processed=1239, rendered=1239, updated=84, transparent=18
16:21:50 [INFO] world.t: processed=673, rendered=673, updated=114, transparent=0
16:21:50 [INFO] TOTALS: processed=2585, rendered=2585, updated=309, transparent=18
16:21:50 [INFO] Triggered update queue size: 20
16:21:50 [INFO] Active render jobs: world
16:21:50 [INFO] Chunk Loading Statistics:
16:21:50 [INFO] Cache hit rate: 36.37%
16:21:50 [INFO] Chunk sets: created=2167, attempted=2167
16:21:50 [INFO] Chunk: loaded=72346, attempted=93213
16:21:50 [INFO] Chunk load times: 66916.45 msec (0.92 msec/chunk)
16:21:50 [INFO] Chunk set load times: 119770.91 msec (55.27 msec/set)
16:21:50 [INFO] Chunk set delay times: 52854.46 msec (24.39 msec/set)
16:21:50 [INFO] Chunk set exceptions: 0
16:21:50 [INFO] World tick list processing calls: 0
76ms (No noticeable server lag).
Longer times for Bukkit, I have VM's running for work, maybe some disk play happening there.
0
Dynmap 1.4 a2
MinecraftForge v6.6.0.497
MCS 1.4.7
Server is quad core 3.2ghz, 4GB of ram (3.5 to java).
Load average is 1.52 average, all from java. This is 0.1 average when dynmap is not crunching out maps. It actually appears like dynmap might be running the server out of memory. I can allocate more ram to test this theory. Up to perhaps 12GB. Currently it's pushed out into swap by 300MB.
I'm the only one on the server. Mods present are Buildcraft, RP2, and Dynmap, but with a non-modified map except the pre-fill. Map was pre-filled out to 2000 chunks in all directions. I asked dynmap to radius render 300 from the middle.
Speaking of, dynmap's helper text is not showing up on plain. Commands at the console, or in-game only return text when dynmap does something, not when you /dynmap help, or any other command. It just gives the status updates on chunks rendered.
Edit: MCS topped out at 4GB. I'll sort the 64 bit issue. But that doesn't solve the really long render times though.