Opened 13 years ago
Closed 7 years ago
#807 closed enhancement (fixed)
Implement profiling for any thread
Reported by: | historic_bruno | Owned by: | |
---|---|---|---|
Priority: | Nice to Have | Milestone: | Alpha 5 |
Component: | Core engine | Keywords: | profiler |
Cc: | Patch: |
Description
Currently the profiler is restricted to the main thread, so e.g. scripts that run in other threads can't use the profiling functions. According to Philip, it's hierarchical and each threads needs its own hierarchy, also timings on other threads are independent of frame rendering. So perhaps the profiler should be designed to support one instance per thread, and then those threads would each use their own local profiler.
Potential areas of benefit:
- Random map scripts
- AI scripts (once multithreaded)
- Pathfinding (once multithreaded)
- ?
Also of interest: #806, which will allow script profiling with JIT enabled.
Change History (1)
comment:1 by , 7 years ago
Milestone: | Backlog → Alpha 5 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Solved in [10465] thanks to Profiler2.