Chunk generator performance survey

[xoft]

I'd like to know the general trend of MCServer's chunk generator's performance. Therefore I added a performance logger in rev 707. I'd like to ask you to post your chunks per second value, as averaged from a few successive log entries:

Code:

[22:41:23] Chunk generator performance: 171.25 ch/s (1033 ch total)
[22:41:25] Chunk generator performance: 166.25 ch/s (1337 ch total)
[22:41:27] Chunk generator performance: 163.83 ch/s (1647 ch total)
[22:41:29] Chunk generator performance: 165.45 ch/s (1996 ch total)
[22:41:31] Chunk generator performance: 166.55 ch/s (2344 ch total)

From here I can see that my average is about 166 chunks per second.

Also post your MCServer revision number, CPU and RAM specs and OS version. If you need help identifying the CPU on Windows, you can use cpu-z ( http://www.cpuid.com )

Please keep in mind that this is not a competition, it is only to help me understand potential bottlenecks and hardware limitations that can affect the generator performance.

So that the results are comparable, you should be using this world.ini as the generator basis:

Code:

[Storage]
Schema=Anvil

[Plants]
MaxCactusHeight=3
MaxSugarcaneHeight=3
IsCropsBonemealable=1
IsGrassBonemealable=1
IsSaplingBonemealable=1
IsMelonStemBonemealable=1
IsMelonBonemealable=0
IsPumpkinStemBonemealable=1
IsPumpkinBonemealable=0
IsSugarcaneBonemealable=0
IsCactusBonemealable=0

[Seed]
Seed=2

[Generator]
BiomeGen=DistortedVoronoi
HeightGenCacheSize=64
HeightGen=Biomal
Structures=OreNests,Trees,WormNestCaves,Ravines
Finishers=SprinkleFoliage,Ice,Snow,Lilypads,BottomLava
CompositionGen=Biomal
DistortedVoronoiCellSize=128
DistortedVoronoiBiomes=
BiomeGenCacheSize=64
BiomalSeaLevel=62
BottomLavaLevel=10

Rev: 709
CPU: Intel Core2Quad Q8300, 2.5 GHz, 4 MiB L2 cache, FSB 333 MHz, DDR2 RAM @ 400 MHz
OS: WinXP 32-bit
Throughput: 166 chunks per second

---

Oh, one more thing: to test the generator performance, you need a way to make it generate chunks An ideal tool for that is the ChunkWorx plugin by Taugeshtu, get it in the Plugin Releases sub-forum. Then use your web browser to connect to webadmin and in the ChunkWorx tab, let it generate an area, I usually do a 25-chunk radial area around some point.

[NiLSPACE]

maybe can you add a snooper setting just like minecraft 1.3 does

[xoft]

No, Never! I hate ET-phone-home programs and I'll never ever write one!
Btw, MC already reports usage via snooper in earlier versions, only in 1.3 they seem to have added some settings for that; before you had no control over it at all.

[NiLSPACE]

ok ok calm down :S I was only proposing it

[FakeTruth]

Code:

[17:31:04] ChunkWorx v.1: REgeneration STARTED!
[17:31:04] ChunkWorx v.1: PROCESSING 100 chunks, (0/1681)
[17:31:04] ChunkWorx v.1: PROCESSING 100 chunks, (100/1681)
[17:31:04] ChunkWorx v.1: PROCESSING 100 chunks, (200/1681)
[17:31:05] ChunkWorx v.1: PROCESSING 100 chunks, (300/1681)
[17:31:06] ChunkWorx v.1: PROCESSING 100 chunks, (400/1681)
[17:31:06] Chunk generator performance: 104.14 ch/s (209 ch total)
[17:31:07] ChunkWorx v.1: PROCESSING 100 chunks, (500/1681)
[17:31:08] ChunkWorx v.1: PROCESSING 100 chunks, (600/1681)
[17:31:08] Chunk generator performance: 103.56 ch/s (416 ch total)
[17:31:09] ChunkWorx v.1: PROCESSING 100 chunks, (700/1681)
[17:31:10] ChunkWorx v.1: PROCESSING 100 chunks, (800/1681)
[17:31:10] Chunk generator performance: 103.14 ch/s (621 ch total)
[17:31:11] ChunkWorx v.1: PROCESSING 100 chunks, (900/1681)
[17:31:12] ChunkWorx v.1: PROCESSING 100 chunks, (1000/1681)
[17:31:12] Chunk generator performance: 102.90 ch/s (826 ch total)
[17:31:13] ChunkWorx v.1: PROCESSING 100 chunks, (1100/1681)
[17:31:14] ChunkWorx v.1: PROCESSING 100 chunks, (1200/1681)
[17:31:14] Chunk generator performance: 101.24 ch/s (1016 ch total)
[17:31:15] ChunkWorx v.1: PROCESSING 100 chunks, (1300/1681)
[17:31:16] Chunk generator performance: 99.53 ch/s (1198 ch total)
[17:31:16] ChunkWorx v.1: PROCESSING 100 chunks, (1400/1681)
[17:31:17] ChunkWorx v.1: PROCESSING 100 chunks, (1500/1681)
[17:31:18] Chunk generator performance: 98.97 ch/s (1390 ch total)
[17:31:18] ChunkWorx v.1: PROCESSING 100 chunks, (1600/1681)
[17:31:18] ChunkWorx v.1 - REgeneration ENDED!
[17:31:20] Chunk generator performance: 98.80 ch/s (1586 ch total)

101.535 chunks per second

Rev: 709


World.ini

Code:

[SpawnPosition]
X=469.000000
Y=256.000000
Z=141.000000

[Storage]
Schema=Anvil

[Plants]
MaxCactusHeight=3
MaxSugarcaneHeight=3
IsCropsBonemealable=1
IsGrassBonemealable=1
IsSaplingBonemealable=1
IsMelonStemBonemealable=1
IsMelonBonemealable=0
IsPumpkinStemBonemealable=1
IsPumpkinBonemealable=0
IsSugarcaneBonemealable=0
IsCactusBonemealable=0

[GameMode]
GameMode=1

[Seed]
Seed=767131738

[Generator]
BiomeGen=DistortedVoronoi
DistortedVoronoiCellSize=96
DistortedVoronoiBiomes=
BiomeGenCacheSize=64
HeightGen=Biomal
HeightGenCacheSize=64
CompositionGen=Biomal
BiomalSeaLevel=62
Structures=Trees,MarbleCaves,OreNests
Finishers=SprinkleFoliage,Ice,Snow,Lilypads,BottomLava
BottomLavaLevel=10

[xoft]

Weird, I was expecting a bit more from a Core i7. It's supposed to be a high-end. But your settings are totally weird, that's probably the cause.

[NiLSPACE]

Its the plugin that generates 100 chunks. I remember that my dual-core also says 100 chunks with that plugin.

[FakeTruth]

Weird, I was expecting a bit more from a Core i7. It's supposed to be a high-end. But your settings are totally weird, that's probably the cause.

It's only 2Ghz

EDIT: I added my world.ini file
Perhaps you should provide a world.ini that should be used for the benchmark

[xoft]

It's only 2 GHz, but it's at least two generations younger. It should've at least matched my performance, if not exceeded. I suspect the low FSB and slow RAM timing. But maybe it's part of the turbo boost technology - when raw computing power is needed, those two are set better?

True, I keep forgetting that our generator is so configurable I'll edit my initial post to include the benchmark world.ini.

STR_Warrior, the plugin queues chunks in groups of 100, because it doesn't want to overload the generator. It waits until there's less than 200 chunks queued in the generator, and only then pushes another group of 100. So the generator should have a steady supply of chunks to generate, while not being overtaxed.

[Luksor]

[23:30:35] Chunk generator performance: 225.66 ch/s (452 ch total)
[23:30:37] Chunk generator performance: 231.65 ch/s (928 ch total)
[23:30:39] Chunk generator performance: 229.90 ch/s (1381 ch total)
[23:30:41] Chunk generator performance: 229.56 ch/s (1839 ch total)
[23:30:43] Chunk generator performance: 229.00 ch/s (2293 ch total)
[23:30:45] Chunk generator performance: 227.84 ch/s (2738 ch total)
[23:30:47] Chunk generator performance: 227.30 ch/s (3187 ch total)
[23:30:49] Chunk generator performance: 226.78 ch/s (3634 ch total)
[23:30:51] Chunk generator performance: 226.70 ch/s (4087 ch total)
[23:30:53] Chunk generator performance: 226.85 ch/s (4544 ch total)
[23:30:55] Chunk generator performance: 227.17 ch/s (5005 ch total)
[23:30:57] Chunk generator performance: 227.49 ch/s (5468 ch total)
[23:30:59] Chunk generator performance: 227.74 ch/s (5930 ch total)
[23:31:01] Chunk generator performance: 228.32 ch/s (6403 ch total)
[23:31:03] Chunk generator performance: 228.22 ch/s (6857 ch total)
[23:31:05] Chunk generator performance: 228.69 ch/s (7329 ch total)

Revision: 709
CPU: Intel Core i5-2400 3.1GHz
RAM: GoodRam 4GB 1333MHz CL9
OS: Windows 7 64bit

I was using ChunkWorx v3.
The server uses ~35% CPU when generating new chunks.