It'd be awesome if d2 could have some kind of timings report, which would be able to tell us how much load each script and each command inside the script are taking on the server
D2 Timings Request
-
BlackCoyote
- Regular

- Posts: 78
- Joined: August 6th, 2016, 1:44 am
D2 Timings Request
I couldn't find a better place to put this so deal with it
It'd be awesome if d2 could have some kind of timings report, which would be able to tell us how much load each script and each command inside the script are taking on the server
It'd be awesome if d2 could have some kind of timings report, which would be able to tell us how much load each script and each command inside the script are taking on the server
- mcmonkey
- Site Admin

- Posts: 299
- Joined: August 5th, 2016, 7:27 pm
- Location: Los Angeles, California, USA
- Contact:
Re: D2 Timings Request
I fixed it.
Yes, three types of timings will reasonably be available:
The Denizen classic event-based timings, so you can see which event is eating how much time.
The generic background Java timings systems.
And... a Denizen2 per-script timer thingy is reasonably likely to be added as well. (Which, I believe, this one is what you're asking about here)
However, "each command inside the script"... is too far imo. A lot of commands will run in so many nanoseconds, and we wouldn't be able to so much as produce a number for these cases, leading to more confusion than anything in these cases. I can see where it'd be useful, you want to measure whether BigImpactCommand1 is worse than BigImpactCommand2 (Where each is, for example, editing an entire chunk-full of blocks or something)
There will be tools available for a script to do precise timing of its own, and if you think you have a situation like the above, it'd be an excellent place to employ precise script timing tools.
Yes, three types of timings will reasonably be available:
The Denizen classic event-based timings, so you can see which event is eating how much time.
The generic background Java timings systems.
And... a Denizen2 per-script timer thingy is reasonably likely to be added as well. (Which, I believe, this one is what you're asking about here)
However, "each command inside the script"... is too far imo. A lot of commands will run in so many nanoseconds, and we wouldn't be able to so much as produce a number for these cases, leading to more confusion than anything in these cases. I can see where it'd be useful, you want to measure whether BigImpactCommand1 is worse than BigImpactCommand2 (Where each is, for example, editing an entire chunk-full of blocks or something)
There will be tools available for a script to do precise timing of its own, and if you think you have a situation like the above, it'd be an excellent place to employ precise script timing tools.
Denizen lead developer. On Discord as
mcmonkey#6666.Who is online
Users browsing this forum: No registered users and 3 guests
