> For the complete documentation index, see [llms.txt](https://docs.bdb.ai/performance-and-resource-benchmarking/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdb.ai/performance-and-resource-benchmarking/performance-and-resource-benchmarking.md).

# Performance & Resource Benchmarking

BDB has implemented a couple of projects in Petabyte Scale in 2021 and 2022. During these 2 years, we have made 6.5, 7.0, and 7.5 versions of the platform. After the 7.6 release BDB has started doing Performance Testing on all modules to share these reports with any existing or Potential Partner or Customer of BDB. This section will have extensive Performance Test Reports on the 7.6 version. BDB also conducts PEN Tests by external Security Agencies and if any Partner or Customer wants a Pen Test report, please write to our Pre-Sales team at <prakash.joshi@bdb.ai>


---

# 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.bdb.ai/performance-and-resource-benchmarking/performance-and-resource-benchmarking.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.
