33 ms·
Yes, but analyze how? In your head? Of course not. But I can work out how the software tools for performance measurement are going to work in my head. I can al
by stcredzero 13y ago
Yes, but analyze how? In your head?
Of course not. But I can work out how the software tools for performance measurement are going to work in my head. I can also work out if the performance degradation of a game loop will be gradual with some degree of reliability and also know how the measurement tools to verify that are going to work.
There is no more "close to the metal"
Long time Smalltalker and Clojurist here. Preaching to the choir you are. However, to minimize risks, one should still understand what one is doing as well as they can beforehand. I'm not saying that your architecture is bad. I'm trying to explain my decision making process with regards to it. Furthermore, if I had more information about how to implement pragmatic performance guarantees or at least a high probability of gradual degradation, and if I knew enough about performance monitoring in the actor architecture, I would probably change my assessment of the risks involved in trying it.
Unless your game runs on a console, there is so much interference from other processes
It's probably going to run on a dedicated server.
Basically, what I've been trying to get across in these threads is: Your architecture sounds really cool but I don't quite have enough information about it to make me want to try it.
Or to put it another way:
"It's really great because of Z!"
"Yes, but I also really need X and Y and I don't know how it would be with X and Y."
"Yeah, you should be able to work all that out, and can't you see that it's really great with Z!?"
"Yes, it's great with Z, but..."