performance
I made a quick FPS comparison, using todayās 0b6cbf7265314 revision from git master, with the glmark2 default test (windowed, 800x600), comparing:
- running natively on an AMD Stoney APU
- running through
gl-streaming
through the loopback network interface - running
glmark2
on a higher-end (QubesOS) laptop, streaming to the AMD Stoney APU through gigabit ethernet
Keep in mind that this is still preliminary code, with no profiling/optimisation done yet (I even removed most upstream optimisations, which were slowing down feature progress).
And all of this, obviously, is just statistics
Potentially interesting information:
- from GLS alone, most tests suffer about 60% drop in FPS, some perform noticeably better, but one (the famous
ideas
scene, which does not render properly to start with) suffers from nearly 90% FPS drop - the tests that show to be the most demanding in the native case usually donāt suffer as much from being used through GLS ā that could be a rather good sign for real-life loads
- if we add a real network in the picture, most tests show 5-10% additional loss, except:
- one test using client-data instead of vbo (where we likely transfer the data several times, no surprise thatās great handicap when that happens over the network)
- several tests show a better score than with GLS alone, which seems to hint that in those particular cases, the more powerful CPU can indeed compensate for part of the loss in GPU throughput (could those be CPU-bound benchmarks of the GPU ? would not sound good)