branchrust_reboot/main/network_profilercancel
22 Commits over 30 Days - 0.03cph!
Compile fix (random include statement)
- Unity editor check and compile fixes on CLIENT/SERVER
- Swapped to Newtonsoft rather than JsonUtility - actually serializing the json properly now
- Expanded the name box
- Add import and export buttons to the ui. imported network data fills out the profiler as you'd expect
- Add names to serialized data so save/load profiles can support naming (as the ids will be invalid when loaded)
- Fix some incorrect server/client entity usages
- Cleanup
- Some clamping to avoid the server exploding
- Set detailed packing data as serializable so its included in the export
- Dont export with pretty print (to save space) brings a 10 second sample from 7MB down to 3MB
- Codegen
Network Profiler
- Can now profile for x seconds via command line
- Export to JSON file
- Import from JSON file
Final profiler window tweaks: supports larger packet rundowns
Capture all missed outgoing packets in client and server
Ensure 'server' is set right on our inbound packets
Record the rest of the inbound packets I missed: group enter, group change, group destroy, world data, voice data, entity flags, entity position
Better effect outgoing packets
- Added RPC name under the info section of RPC packets
- Added global filters for server/client realms
- Added packet type breakdown of the top packets
- Clean restyle of the net graph
First draft of a network profiler. Featuring:
- Simple packet stats
- Advanced stats (entity name, packet size, timestamp etc)
- Filtering via timestamp, name, type, direction, realms
- Per entity bandwidth usage, showing how much % of the bandwidth is taken up by what packets
Store:
- RPC inbound/outbound
- SyncVar inbound/outbound
- PackedSyncVar inbound/outbound
- Effect inbound/outbound
Missed some metrics here and there, but critically I've managed to grab the id its going to for each one
Setup data structures to store more detailed packet information, this will be stored and handled locally rather than being sent off for analytics.
Data will be stored in a big ass circular buffer that we can then sort through to do the analytics.
These include:
- Basic data we stored before (byte size, type, etc)
- Associated entity with the packet
- Optional full packet data
- Timestamp
