ID:2307055
 
Applies to:DM Language
Status: Open

Issue hasn't been assigned a status value.
The ability to know (in code):

  • Processor id (for if we need to run shell commands on our process)
  • Real processor level cpu usage (world.cpu measures something different)
  • Real processor level memory usage
  • Byond memory stats printed when you hit control + m (Ideally as a keyed list with string numbers, we can convert to num in code to get a float approximation for mathing/avging while still printing the exact version to log files
  • Full profile access:
    • Commands to start/stop/clear profiles
    • The ability to iterate thru a profile and/or copy it's current state as a list
    • The ability to write a profile to an arbitrary file
    • It's worth pointing out that the reason we want in code access to profiles is so we can take repeated small snapshots to section out profiles based on things, and then group the small snapshots together. With /tg/'s MC we have alot of contextual information about what is about to happen code wise. The ability to, say, seperate profiles out to what subsystem is running would be nice. The ability to maybe only profile during times of lag would be nice



As an aside, profiles could really use some extra fields, things like lowest run, longest run, time spent in tick overrun (where world.tick_usage is higher than 100).