> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/apis-and-integration/adding-benchmarking-to-any-script.md).

# Adding benchmarking to any script

> **Applies to:** ProSBC 3.1; Tmedia 2.9, 2.10, 3.0, 3.2

Routing scripts must be well designed to maximize the performance of a system. To help in the evaluation of the performance of a script (or part of a script), use this benchmarking tool.

Three lines need to be added to the script.

At the start of the script:

```
require 'benchmark'
```

In the main class, before the function to evaluate:

1. 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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/how-to-troubleshoot-call-routing/README.md#using-the-applications-log-files)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/apis-and-integration/adding-benchmarking-to-any-script.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.