MicroGraph Performance Test

[StarFire]

Just been running performance test comparison between actions, Lua and Micrograph.

Four presets were made for each test. Each preset was scripted to make a cube shape rotate by:
1) action rotate
2) Lua entity.turn(...) in the micro script update loop
3) micro graph containing a rotate module.
4) control just a cube!

A simple scene script was then used to spawn the cube preset in an array of x=30 x z=30. So we had a screen full of 900 rotating cube and checked on the metrics, the results are as follows.

1) Action: 330 frames per second
2) Lua: 135 frames per second
3) Micrograph: 230 frames per second
4) Control: 440 frames per second

So the new visual module system will give better performance than Lua and be more friendly to use. Still it is best to have developed systems in actions where can be. It does make a good argument for a Skyline SDK at some point. I am now wondering what the performance hit would be from c# mono, maybe something to check out at another time?

So for most cases full game systems should be created dev side as actions, but where user customization is require the module system is the best bet.

[TattieBoJangle]

Damm Lua that's some drop

[SolarPortal]

yeah, finally getting to develop a module or two myself now System is much faster and easier to use.

[epsilonion]

Can not wait to see c# implemented and see how that compaires.


Would have thought scripting would have been better than that tbh. I am sure there would be some tweaking to do later on in development closer to v1

[StarFire]

What we are seeing is the time honored problem of interpreted languages over compiled languages and compiled code will always win, this is why actions win hands down. Lua is one of the fastest of the interpreted languages and most flexible.
I really don't know how c# will perform as it does get compiled but still gets passed to the run time interpreter which will slow it down. I dont think it will out perform modules and certainly not beat actions.

When you look at it all of the options perform great, there are 1000's of operation per loop as each object processes values and updates the parent objects render node . Lua's bottle neck is in the parsing of the commands as they get passed between the core and run-time systems.