×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 2/22/2018 2:30 PM, Craig Richards wrote:
And I fear that the call stack one is a bit expensive to do every time
Don't fear the expense - measure it.
If you implement the 'who triggered me' code as a sub-procedure, you can
swap out different methods very quickly. Run a hundred thousand tests
of each method and you'll have reasonable numbers with which to base a
decision.
Along those lines, it can be very enlightening to instrument all of the
various sub-procedures / code blocks. I found my intuition wasn't as...
precise as actual elapsed time measurements.
Speaking of actual time, does your organisation have a performance spec
for this application? The closest my organisation gets to a performance
spec is vague hand waving when something 'is taking too long'. The net
result is that performance requirements tend to be somewhat more
flexible than I myself start off believing.
midrange.com
