Adding Benchmarking to your Routing scripts
From TBwiki
(Difference between revisions)
(Added end in do loop) |
(Updated the display function) |
||
| Line 24: | Line 24: | ||
In the main class, after the function to evaluate:<br> | In the main class, after the function to evaluate:<br> | ||
end #End benchamrking | end #End benchamrking | ||
| − | log_trace 3, "It took #{bm.real | + | log_trace 3, "It took #{'%.6f' % bm.real} seconds to do this function" |
This will print in the gateway application log the time it took to run this function. | This will print in the gateway application log the time it took to run this function. | ||
<br> | <br> | ||
Click here to know [[How_to_troubleshoot_call_routing#Using_the_applications_log_files|how to get the log files]] | Click here to know [[How_to_troubleshoot_call_routing#Using_the_applications_log_files|how to get the log files]] | ||
Latest revision as of 07:27, 31 March 2021
| This article applies to: | Product | Version |
| ProSBC | 3.1 | |
| Tmedia | 2.9, 2.10, 3.0, 3.2 |
Routing scripts need to be well designed to allow for maximum performance of a system.
To help evaluating the performance of a script (or part of a script), you can use this benchmarking tool.
Three lines need to be added.
At the start of the script:
require 'benchmark'
In the main class, before the function to evaluate:
# Start benchmarking bm = Benchmark.measure do
In the main class, after the function to evaluate:
end #End benchamrking
log_trace 3, "It took #{'%.6f' % bm.real} seconds to do this function"
This will print in the gateway application log the time it took to run this function.
Click here to know how to get the log files
