Updates tests README to mention performance testing

Author: pranavm-nvidia

tripy/tests/README.md

@@ -130,3 +130,26 @@ Any caption other than `Example` will have a prefix of `Example: ` prepended to
 
 **NOTE: The docstrings must *not* import `tripy`, `numpy`, or `torch`. They will be imported**
     **automatically as `tp`, `np`, and `torch` respectively. Any other modules will need to be imported.**
+
+
+### Performance Tests
+
+In addition to functional tests, we also run performance tests of three kinds:
+
+1. Regression tests, which compare current Tripy performance to historical data
+    to ensure we don't regress. We use the
+    [`pytest-benchmark`](https://pytest-benchmark.readthedocs.io/en/latest/)
+    plugin to gather data and the
+    [Continuous Benchmark GitHub Action](https://github.com/marketplace/actions/continuous-benchmark)
+    for regression testing.
+
+    You can view graphs and charts of the historical data by opening the
+    [`index.html` file from the `benchmarks` branch](https://github.com/NVIDIA/TensorRT-Incubator/blob/benchmarks/dev/bench/index.html)
+    in a browser.
+
+2. Comparative tests, which compare Tripy and `torch.compile`.
+
+3. Overhead tests, which check the overhead introduced by Tripy as compared
+    to running the underlying MLIR executable by itself. This is done by measuring
+    how long it takes to run an empty executable since in that case, all the time
+    is taken by the Tripy wrapper code.