> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/call-routing-routes-and-naps/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](/operations-and-support/troubleshooting/how-to/how-to-troubleshoot-call-routing.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/other-pages/call-routing-routes-and-naps/adding-benchmarking-to-any-script.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.