06-10-2013, 06:28 AM
It wouldn't increase performance at all.
Currently, the tick thread locks the chunkmap's CS, performs whatever it needs to, releases the CS, and waits for the next tick; the other threads can interact with the chunkmap.
In your version, the tick thread performs whatever it needs, then it locks the commandqueue's CS, executes the commands, releases the CS and waits for the next tick.
There's nothing saved and nothing gained; but it gives additional complexity and additional burden on the tick thread.
Currently, the tick thread locks the chunkmap's CS, performs whatever it needs to, releases the CS, and waits for the next tick; the other threads can interact with the chunkmap.
In your version, the tick thread performs whatever it needs, then it locks the commandqueue's CS, executes the commands, releases the CS and waits for the next tick.
There's nothing saved and nothing gained; but it gives additional complexity and additional burden on the tick thread.