Performance of Zero-K

Impart infolog. Take a screenshot with /debug enabled. Do and link a benchmark.

A restart is needed for some changes. Some outdated benchmarks are under Help. Updating them is not a particularly difficult task, but it takes time, so someone could step up and do it.

No.

First thing to try: Chili Deluxe Player List has terrible performance. Remove it and use the default one.

Your average FPS was around 10, which seems ok. The benchmark doesn't have players in it so it won't measure the playerlist.

quote: Dumb question: how can a 2D player list with text, numbers and simple graphics like bars significantly impact performance? Has there been any attempt to speed up?

There is no bound on how poorly you can make a piece of code perform. Deluxe playerlist was never (or at least not for a very very long time) enabled by default because it has terrible performance. It was based on the default playerlist, which was also terrible. I completely replaced the default playerlist with a cheap implementation. If anyone wants to write a version of deluxe with the replacement as a base, then they are free to do so. In the meantime people with deluxe have to suffer the performance cost.

The benchmark is a stress test. What is your FPS when spectating a game with about 600 units?

quote: if game never goes below 30FPS in cluster

I never had 30 fps in cluster after midgame when there is mass units. Game eat single core so you need CPU with good single core speed.



I didn't even know that Chili delux player list could impact performance in such levels. However i found that my ATI GPU preformed very bad on win7 64 bit. When i changed it with 1050 TI then my performance was greatly improved.

A lot of the cost of deluxe playerlist shows up as activity in the Chili Framework. The good playerlist is "Chili Crude Player List".

quote: Surely presenting such simple graphics ought not to eat up so many processing cycles?

This isn't how computers work. Literally anything can be done arbitrarily poorly.

I don't know. The answers to those questions are unimportant. Where does knowing exactly how bad the performance is get us? Have you tried to read and improve other people's code before, or am I talking across a large gulf of understanding?

The author list says "CarRepairer, KingRaptor, CrazyEddie", which fits with my memory of who was generally writing the UI, but I mostly kept out of the original chili UI widgets because of all the crazy code.

At some point (I think during a November) I completely rewrote the bottom three parts of the UI (not the minimap) because they had terrible performance similar to the terrible performance of the playerlist. This was far easier than trying to read and significantly modify other people's code. I did not rewrite the playerlist because it looked like a big boring thankless task and there were other things to do.

Over the subsequent years I tried to get other people to take on the fairly well-defined task of writing a playerlist, so I could do other boring important that needed doing, but nobody managed to write a complete replacement. DeinFreund got the closest with the Tab playerlist (which also has terrible performance), which a least eased up on the amount of information that a rewritten playerlist would "need" to display. Eventually I got fed up with the one remaining widget of terrible performance, and the new Crude Playerlist is the result.

Unfortunately, zerok's engine aka springrts is not using vulkan so there is significant cpu overhead and this game is unforutnately cpu intensive on top of that api overhead. You need a more recent cpu to do good for this game.