> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/developers/developer-tooling/benchmarking.md).
# Benchmarking
To test the performance of Eclipse Testnet, you can run our benchmarking script. The following test benchmarks AMM swaps to assess the TPS of Eclipse Testnet.
## Prerequisites[](https://icarus131.github.io/devcookbook/docs/Benchmarking#pre-requisites)
* [node.js](https://nodejs.org/en/download/)
* [git](https://git-scm.com/downloads)
Once you have the above installed, clone the benchmarking repository:
```bash
git clone https://github.com/Eclipse-Laboratories-Inc/eclipse-benchmarking/
```
## Running Benchmarking Test[](https://icarus131.github.io/devcookbook/docs/Benchmarking#running-the-benchmarking-tests)
Navigate to the `token_swap` folder after cloning the repository. Install ts-node by running the following command:
```bash
npm i -g ts-node
```
{% hint style="warning" %}
You might have to give super user or admin permissions to install globally or use the `-g` flag.
{% endhint %}
To install the dependencies, run the following command:
```bash
npm i
```
Make sure to run this command inside the `token_swap` folder. The final step is to run the benchmarking tests using the following command:
```bash
ts-node spam.ts
```
This runs 10 instances of an AMM performing any specified number of swaps.
## Modifying Benchmarking[](https://icarus131.github.io/devcookbook/docs/Benchmarking#modifying-the-benchmarking-tests)
The default test is 275 swaps. To modify the number of swaps, modify line 63 in the `benchmark.ts` file inside the `token_swap` folder. The following is the code snippet to modify:
```javascript
...
await mintTo(connection, payer, mintA, userAccountA, owner, SWAP_AMOUNT_IN);
console.log("Run test: benchmark swap");
await benchmarkSwap(275);
console.log("Success\n");
```
If you've followed the steps successfully, you should see an output similar to the following:
---
# 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://docs.eclipse.xyz/developers/developer-tooling/benchmarking.md?ask=&goal=
```
`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.
