# Performance Test

Like word on the street said(no way it's just us saying!) or you may saw in previous chapters(maybe multiple times), WAMR is a **lightweight** standalone WebAssembly (WASM) runtime with **small footprint**, **high performance** and highly configurable features.

Well, you don't have to take our word for it. You could run the [Benchmarks in our repo](https://github.com/bytecodealliance/wasm-micro-runtime/tree/main/tests/benchmarks) and decide whether the performance is good enough.

We provide multiple benchmarks that you could try:

* [PolyBench](https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/performance-benchmark/polybench)
* [CoreMark](https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/performance-benchmark/coremark)
* [Sightglass](https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/performance-benchmark/sightglass)
* [JetStream2](https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/performance-benchmark/jetstream)

For the memory footprint, you can refer to the links below.

* [Performance and footprint data](https://github.com/bytecodealliance/wasm-micro-runtime/wiki/Performance): checkout [here](https://github.com/bytecodealliance/wasm-micro-runtime/wiki/Performance) for the performance and footprint data

And in the next section, we provide tutorials on memory usage tuning. You can [profile memory usage](https://wamr.gitbook.io/document/tutorial/build-tutorial/build_wamr#enable-memory-profiling-experiment) and [tunning memory usage](https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/memory_tune)


---

# Agent Instructions: 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:

```
GET https://wamr.gitbook.io/document/wamr-in-practice/advance-tutorial/performance-benchmark.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.