| 9 | | The biggie is the overhead being used to create the strings for tr_deepLog(). It's not very expensive in any place that it's called, but is showing up at a little over 1% in a dozen different places. We should add a check to see if deep logging is enabled ''before'' creating those strings. |
| | 9 | tr_buildPath() is taking up a little over 3% by calling vsnprintf(). printf() is overkill here, since no string formatting is necessary -- we can simply malloc the path and memcpy the path fragments. |
| | 10 | |
| | 11 | The biggie is the overhead being used to create the strings for tr_deepLog(). It's not very expensive in any place that it's called -- only a little over 1% in any given place -- but shows up in over a dozen places, so the cumulative footprint is large. We can avoid all of that by checking to see if deep logging is enabled ''before'' creating those strings. |
