Tech talk - cpu usage analysis

[FlipFlop™]

Some time ago I did some timing profiling on Flexhub and made an analysis of the resulting data.
Meanwhile some improvements have been made based on this analysis, so it's not very accurate anymore, but might be interesting to look a bit behind the scenes for the geeks among us.

At the moment there are a lot of os.clock() calls in the code to provide timing info in the hub for the !coreinfo command, this is for debugging purposes. After beta these os.clock() calls will be dramatically reduced.

Here's the graph with the summary, or click http://www.flexhub.org/images/Flexhub-CPU.jpg for the big version:



Ofcourse any comments or critics are welcome!

[TraN]

the biggest part is waiting, thats good 
what part is the one involving os.clock()? the one called "clock"?

[FlipFlop™]

Yep, so it takes quite a large bit of the total processing time now, about 1% of the total 15% that the application takes cpu-time, so theoretically reducing the timings for gathering statistics on operations can  increase the hubs performance up to around 8%.

[FlipFlop™]

Some profiling has now been done on FlexHub svn 1075, we think there's still quite some room for improvement, which will mean the hub will run with less cpu usage, and a higher max usercount is possible. Currently max usercount is around 1500, if the system has a decent cpu.

Click the links to see the full resolution images.

http://flexhub.org/images/Flexhub-Profiling-cpu-60logins.jpg



http://flexhub.org/images/Flexhub-Profiling-calls-60logins.jpg