# Notes on Performance The current discourse in cryptocurrencies focuses on “maximum TPS” as the key defining performance metric, and one often finds various outlandish claims about it. For more details on why these numbers don’t matter, we recommend [this article from the Nervos Network](https://medium.com/nervosnetwork/forget-about-the-tps-competition-df40a45fdad8). {% hint style="info" %} **NOTE** There are more issues with regard to “maximum TPS metrics” that are not mentioned in the article {% endhint %} We’ll have to eat humble pie and say that some of the existing Cronos POS Chain materials fall into similar fallacies (despite being written with the word “aim” and intended to be seen in the potential Layer-2 context). In the future, once the system reaches a certain maturity, we’d like to establish metrics (e.g. the 95th percentile of end-to-end transaction latency) that are more meaningful for user experience. We would try to benchmark against these metrics, ideally in diverse settings (rather than “the best case where nothing ever crashes”) and using estimated real workloads. --- # 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://docs.cronos-pos.org/for-node-hosts/notes-on-performance.md?ask= ``` 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.