Can you explain what working on performance means, the same way you explained working on stability?
TL;DRPerformance covers client, hybrid and server frame rate, load times, memory use, resource use, and network latency and bandwidth, with the emphasis on setting much stricter budgets.
Sure. Performance is a larger one. And so performance touches on the client, the hybrid and the server. The hybrid is the replicant that takes care of the networking. And so performance is about obviously frame rate, to begin with, on the client and on the server. We talked earlier about server optimizations. It's about loading times. So making sure that the load times are acceptable in all kinds of areas. I'm not just talking about the loading screen, I'm talking about loading an asset, streaming in an area, fully initializing a full location, right? That's the load times I'm talking about. Memory utilization, so making sure that we use memory efficiently, that we don't go above our memory budgets. Same thing here, the keyword is budgeting. So we need to have way stricter budgets. We need to work on that area. And then finally, resource utilization of your machine in general, but also network connections. So latency and bandwidth, connectivity and stability of the connection in general, that need to be improved. So that's what working on performance is. So stability is one area, performance is another one.