Termporarily remove the Performance page from the website (#12650)

* Termporarily remove the Performance page from the website

* Update preformance links to point to doc's relese version or latest existing page.

* Fixup another link

content/en/blog/2019/performance-best-practices/index.md

@@ -108,6 +108,6 @@ For a mesh with 1000 RPS across 16 connections, Istio 1.2 adds just **3 millisec
 Istio's performance depends on your specific setup and traffic load. Because of this variance, make sure your test setup accurately reflects your production workloads. To try out the benchmarking scripts, head over [to the Istio Tools repository](https://github.com/istio/tools/tree/3ac7ab40db8a0d595b71f47b8ba246763ecd6213/perf/benchmark).
 {{< /tip >}}
 
-Also check out the [Istio Performance and Scalability guide](/docs/ops/deployment/performance-and-scalability) for the most up-to-date performance data.
+Also check out the [Istio Performance and Scalability guide](https://archive.istio.io/v1.16/docs/ops/deployment/performance-and-scalability) for the most up-to-date performance data.
 
 Thank you for reading, and happy benchmarking!

content/en/blog/2022/cryptomb-privatekeyprovider/index.md

@@ -173,7 +173,7 @@ spec:
 
 The potential performance benefit depends on many factors. For example, the size of the cpuset Envoy is running on, incoming traffic pattern, encryption type (RSA or ECDSA), and key size.
 
-Below, we show performance based on the total latency between k6, gateway and Fortio server. These show relative performance improvement using the CryptoMB provider, and are in no way representative of Istio's [general performance or benchmark results](/docs/ops/deployment/performance-and-scalability/).  Our measurements use different client tools (k6 and fortio), different setup (client, gateway and server running on separate nodes) and we create a new TLS handshake with every HTTP request.
+Below, we show performance based on the total latency between k6, gateway and Fortio server. These show relative performance improvement using the CryptoMB provider, and are in no way representative of Istio's [general performance or benchmark results](https://archive.istio.io/v1.16/docs/ops/deployment/performance-and-scalability/).  Our measurements use different client tools (k6 and fortio), different setup (client, gateway and server running on separate nodes) and we create a new TLS handshake with every HTTP request.
 
 We have [published a white paper](https://www.intel.com/content/www/us/en/architecture-and-technology/crypto-acceleration-in-xeon-scalable-processors-wp.html) with general cryptographic performance numbers.
 

content/en/news/releases/1.1.x/announcing-1.1/_index.md

@@ -26,7 +26,7 @@ The theme for 1.1 is Enterprise Ready. We’ve been very pleased to see more and
 more companies using Istio in production, but as some larger companies tried to
 adopt Istio they hit some limits.
 
-One of our prime areas of focus has been [performance and scalability](/docs/ops/deployment/performance-and-scalability/).
+One of our prime areas of focus has been [performance and scalability](https://archive.istio.io/v1.1/docs/ops/deployment/performance-and-scalability/).
 As people moved into production with larger clusters running more services at
 higher volume, they hit some scaling and performance issues. The
 [sidecars](/docs/concepts/traffic-management/#sidecars) took too many resources
@@ -36,7 +36,7 @@ resource hungry.
 
 We’ve done a lot of work to make both the data plane and the control plane more
 efficient. You can find the details of our 1.1 performance testing and the
-results in our updated [performance ans scalability concept](/docs/ops/deployment/performance-and-scalability/).
+results in our updated [performance ans scalability concept](https://archive.istio.io/v1.1/docs/ops/deployment/performance-and-scalability/).
 
 We’ve done work around namespace isolation as well. This lets you use
 Kubernetes namespaces to enforce boundaries of control, and ensures that your

content/en/news/releases/1.1.x/announcing-1.1/change-notes/index.md

@@ -89,7 +89,7 @@ concise list of things you should know before upgrading your deployment to Istio
   [gateways](/docs/concepts/traffic-management/#gateways).
 
 - **Performance and Scalability Improvements**. Tuned the performance and
-  scalability of Istio and Envoy. Read more about [Performance and Scalability](/docs/ops/deployment/performance-and-scalability/)
+  scalability of Istio and Envoy. Read more about [Performance and Scalability](https://archive.istio.io/v1.1/docs/ops/deployment/performance-and-scalability/)
   enhancements.
 
 - **Access Logging Off by Default**. Disabled the access logs for all Envoy