It would be very useful for figuring out whether a cache was useful, by recording how often a method was called with different / same parameters and so could make effective use of a cache.
The feature doesn't make sense because profiler will perform instrumentation for each call to distinguish between methods. It is not possible in "Sampling" and "Timeline" mode. This kind of instrumentation would be even more complicated than "Line-by-line" mode would cause huge overhead. Profiling results will be irrelevant in terms of performance in this case.
It does make some sense in Tracing mode however, when accurate call counts are already returned. May be it should be opt-in to avoid excessive overhead. Ie select specific methods to capture
Hi.
This feature is not supported.
It would be very useful for figuring out whether a cache was useful, by recording how often a method was called with different / same parameters and so could make effective use of a cache.
The feature doesn't make sense because profiler will perform instrumentation for each call to distinguish between methods. It is not possible in "Sampling" and "Timeline" mode. This kind of instrumentation would be even more complicated than "Line-by-line" mode would cause huge overhead. Profiling results will be irrelevant in terms of performance in this case.
It does make some sense in Tracing mode however, when accurate call counts are already returned. May be it should be opt-in to avoid excessive overhead. Ie select specific methods to capture
David,
Thank you for your feedback. We'll think about what we can do about it.