MantisBT - Zandronum |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004090 | Zandronum | [All Projects] Suggestion | public | 2023-01-20 05:30 | 2024-01-10 03:14 |
|
| Reporter | WaTaKiD | |
| Assigned To | DrinkyBird | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | |
| Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 |
| Product Version | 3.1 | |
| Target Version | 3.2 | Fixed in Version | 3.2 | |
|
| Summary | 0004090: improve the dumptrafficmeasure ccmd's sorting |
| Description | dumptrafficmeasure is a handy tool for finding and optimizing bandwidth hungry actors/scripts
said tool could itself be optimized by listing actors/scripts by their traffic, as opposed to having to scour a potentially long list of scrambled entries, we could instead just glance at the first (or last?) few entries |
| Steps To Reproduce | |
| Additional Information | other ideas from discord:
Trillster: ascending order may be more ideal for console, given it'll only show the most recent lines if you've got a bunch of different actors in play
Trillster: so the highest count actors would always show at the bottom of the list
Kaminsky: There could be an optional parameter to order entries either in ascending or descending order.
there was also a bit about color coding the traffic values depending on size but i feel thatll get complicated, and not all consoles display color |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2023-01-20 05:30 | WaTaKiD | New Issue | |
| 2023-01-20 05:37 | WaTaKiD | Note Added: 0022706 | |
| 2023-01-20 05:45 | Kaminsky | Note Added: 0022707 | |
| 2023-01-20 05:45 | Kaminsky | Target Version | => 3.2 |
| 2023-03-19 21:39 | DrinkyBird | Note Added: 0022813 | |
| 2023-03-19 21:51 | DrinkyBird | Assigned To | => DrinkyBird |
| 2023-03-19 21:51 | DrinkyBird | Status | new => needs testing |
| 2024-01-02 08:11 | Ru5tK1ng | Note Added: 0022970 | |
| 2024-01-10 03:14 | Ru5tK1ng | Resolution | open => fixed |
| 2024-01-10 03:14 | Ru5tK1ng | Fixed in Version | => 3.2 |
| 2024-01-10 03:14 | Ru5tK1ng | Status | needs testing => resolved |
|
Notes |
|
|
|
Kaminsky: Something else worth mentioning that wasn't discussed here or in the ticket: if there's no actor or script traffic dump entries, then it shouldn't print the "Network traffic (in bytes) caused by actor code pointers:" or "Network traffic (in bytes) caused by ACS scripts:" messages.
Kaminsky: If there's no traffic dump at all, then it should probably print something like "there's no network traffic dump available". |
|
|
|
|
Samuzero15tlh: could be possible to add the number of actors that are causing the traffic delays?
Perhaps this could also be useful information to include in the traffic dump? |
|
|
|
|
|
|
|
|
Tested with r231220. dumptrafficmeasure worked as described in the OSDN changelog. Adding the desc parameter sorted the lists from largest to smallest.
Is the amount of actors going to be added to the traffic dump? If not then this issue is pretty much done. |
|