From fca641722c0193a0a978ae7b88c0f110fe291fe4 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Fri, 12 Sep 2025 11:15:31 +0200
Subject: [PATCH 1/5] Update guide Enterprise File Storage - Concepts de
 performances

Replace o(ctet) by B(yte)
Add fio examples
---
 .../guide.fr-fr.md                            | 57 +++++++++++++++++--
 1 file changed, 51 insertions(+), 6 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
index 8514108b027..64c26161e3a 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Concepts de performances
 excerpt: "Découvrez les concepts liés au provisionnement, au suivi ainsi qu'au test des performances de la solution Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objectif
@@ -19,19 +19,19 @@ La notion de « niveau de service » est un élément important dans l’offre E
 - la taille de bloc ;
 - le modèle d’accès séquentiel ou aléatoire.
 
-A ce jour, Enterprise File Storage fournit et garantit des objectifs de performances de **64 Mo/s par To et 4000 IOPS par To**.  Les capacités provisionnées des services ont donc un impact direct sur les performances disponibles pour votre service.
+A ce jour, Enterprise File Storage fournit et garantit des objectifs de performances de **64 MB/s par TB ou 4000 IOPS par TB selon le type d'I/O**.  Les capacités provisionnées des services ont donc un impact direct sur les performances disponibles pour votre service.
 
 Cette information est importante lorsque vous concevez votre architecture de stockage. Prenons trois exemples pour l’illustrer :
 
-- **Exemple n°1** : votre application nécessite un débit théorique d’environ **430 Mo/s**. Pour cela, vous devez provisionner au moins **7 To** de stockage. En effet, un rapide calcul (**430/64 = 6,72**) permet d’estimer la capacité minimale nécessaire pour atteindre ce débit.
+- **Exemple n°1** : votre application nécessite un débit théorique d’environ **430 MB/s**. Pour cela, vous devez provisionner au moins **7 TB** de stockage. En effet, un rapide calcul (**430/64 = 6,72**) permet d’estimer la capacité minimale nécessaire pour atteindre ce débit.
 
-- **Exemple n°2** : votre infrastructure nécessite **4500 IOPS** et un volume de données de **1 To**. Pour cela, vous devez provisionner **2 To** pour obtenir les **4500 IOPS nécessaires**. Plus spécifiquement dans ce cas, vous bénéficierez de **8000 IOPS** sur la capacité provisionnée. Il s’agit donc de sur-provisionner votre service afin d’assurer le niveau de performances souhaité.
+- **Exemple n°2** : votre infrastructure nécessite **4500 IOPS** et un volume de données de **1 TB**. Pour cela, vous devez provisionner **2 TB** pour obtenir les **4500 IOPS nécessaires**. Plus spécifiquement dans ce cas, vous bénéficierez de **8000 IOPS** sur la capacité provisionnée. Il s’agit donc de sur-provisionner votre service afin d’assurer le niveau de performances souhaité.
 
-- **Exemple n°3** : votre application ne nécessite pas de performance en particulier mais un volume de stockage de plus de **60 To**. Dans ce cas, il est préférable de s’orienter vers le service de stockage [NAS-HA](/links/storage/nas-ha), plus économique et permettant d’atteindre des capacités supérieures à 58 To par service.
+- **Exemple n°3** : votre application ne nécessite pas de performance en particulier mais un volume de stockage de plus de **60 TB**. Dans ce cas, il est préférable de s’orienter vers le service de stockage [NAS-HA](/links/storage/nas-ha), plus économique et permettant d’atteindre des capacités supérieures à 58 TB par service.
 
 ### Volumes et qualité de services (QoS)
 
-Pour rappel, un volume est une partition du service (aussi appelée « pool » ou « pool de capacité »). Lors de votre commande, vous provisionnez une capacité pour votre service. Une fois le service livré, vous serez amené à créer vos volumes en mettant à disposition un quota allant de 100 Go à 29 To par volume. 
+Pour rappel, un volume est une partition du service (aussi appelée « pool » ou « pool de capacité »). Lors de votre commande, vous provisionnez une capacité pour votre service. Une fois le service livré, vous serez amené à créer vos volumes en mettant à disposition un quota allant de 100 GB à 29 TB par volume. 
 
 Retrouvez ci-dessous la hiérarchie d’un service de stockage Enterprise File Storage :
 
@@ -66,11 +66,56 @@ L’outil [FIO](https://github.com/axboe/fio) vous permet de tester plusieurs sc
 - le nombre de FIO workers ;
 - le modèle d’accès (lecture/écriture/séquentiel/aléatoire), etc.
 
+Ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteint pour un service EFS de 1TB:
+
+**Lecture aléatoire - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Ecriture aléatoire - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Lecture aléatoire - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Ecriture aléatoire - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+``` 
+**Lecture séquentielle - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+``` 
+**Ecriture séquentielle - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Lecture séquentielle - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+``` 
+**Ecriture séquentielle - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 Retrouvez plus d'informations sur [la documentation de FIO](https://fio.readthedocs.io/en/latest/index.html).
 
+#### Vous avez aussi la possibilité d'utiliser d'autres outils open-source comme :
+
+> nfsiostat (https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+
+> NFStest (https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+
+> nfstrace (https://github.com/epam/nfstrace)
+
+
 ## Aller plus loin
 
 Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services.
 
+
 Échangez avec notre communauté d’utilisateurs sur Discord : <https://discord.gg/ovhcloud>
 

From 98cd374f70da0fa14471137aa837b4793114096f Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Fri, 12 Sep 2025 14:13:36 +0200
Subject: [PATCH 2/5] Update Enterprise File Storage - Performance concepts

Add fio examples
---
 .../guide.en-gb.md                            | 49 ++++++++++++++++++-
 1 file changed, 48 insertions(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
index 71671ab8d38..ee483e4a2fb 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
@@ -66,8 +66,55 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+``` 
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+``` 
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+``` 
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+
+#### You can also use other open-source tools such as:
+
+> nfsiostat (https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+
+> NFStest (https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+
+> nfstrace (https://github.com/epam/nfstrace)
+
+
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.

From dc214c5d3d440b211f964d09d4154669c5258e68 Mon Sep 17 00:00:00 2001
From: Yoann Cosse <yoann.cosse@ovhcloud.com>
Date: Fri, 12 Sep 2025 17:31:16 +0200
Subject: [PATCH 3/5] FR-EN duplication

---
 .../guide.en-asia.md                          |  46 ++++++-
 .../guide.en-au.md                            |  46 ++++++-
 .../guide.en-ca.md                            |  46 ++++++-
 .../guide.en-gb.md                            |  19 +--
 .../guide.en-ie.md                            |  46 ++++++-
 .../guide.en-sg.md                            |  46 ++++++-
 .../guide.en-us.md                            |  46 ++++++-
 .../guide.es-us.md                            | 124 ++++++++++++------
 .../guide.fr-ca.md                            |  53 +++++++-
 .../guide.fr-fr.md                            |  11 +-
 10 files changed, 403 insertions(+), 80 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
index ee483e4a2fb..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-gb.md
@@ -84,11 +84,11 @@ fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=
 **Random write - Bandwidth max**
 ```
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
-``` 
+```
 **Sequential read - IOPS max**
 ```
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
-``` 
+```
 **Sequential write - IOPS max**
 ```
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
@@ -96,7 +96,7 @@ fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k
 **Sequential Read - Bandwidth max**
 ```
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
-``` 
+```
 **Sequential write - Bandwidth max**
 ```
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
@@ -104,16 +104,11 @@ fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k
 
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
 
-#### You can also use other open-source tools such as:
-
-> nfsiostat (https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
-
-> NFStest (https://wiki.linux-nfs.org/wiki/index.php/NFStest)
-
-> nfstrace (https://github.com/epam/nfstrace)
-
-
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
 
 ## Go further
 
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
index 3edfe69084a..a794f50fb9f 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
@@ -27,7 +27,7 @@ This information is important when you design your storage architecture. Let’s
 
 - **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
 ### Volumes and quality of services (QoS)
 
@@ -66,10 +66,52 @@ The [FIO](https://github.com/axboe/fio) tool allows you to test several scenario
 - The number of FIO workers
 - The access model (read/write/sequential/random), etc.
 
+
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**You can also use other open-source tools such as:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Go further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
\ No newline at end of file
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
index 3f6e4c95cab..bad7143fdd2 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
@@ -4,76 +4,114 @@ excerpt: "Descubra los conceptos relacionados con el aprovisionamiento, el segui
 updated: 2022-11-30
 ---
 
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
+## Objective
 
-## Objetivo
+Learn about the concepts of provisioning, tracking, and performance testing for [Enterprise File Storage](/links/storage/enterprise-file-storage).
 
-Descubra los conceptos relacionados con el aprovisionamiento, el seguimiento y la prueba del rendimiento de la solución [Enterprise File Storage](/links/storage/enterprise-file-storage).
+## Instructions
 
-## Procedimiento
+### Performance monitoring
 
-### Seguimiento del rendimiento
+The concept of “service level” is an important element in the Enterprise File Storage solution. It defines the levels of performance that can be achieved for each provisioned service. File system performance is typically defined by several elements:
 
-El concepto de "nivel de servicio" es un elemento importante de la solución Enterprise File Storage. Establece los niveles de rendimiento alcanzables para cada servicio aprovisionado. El rendimiento de un sistema de archivos suele definirse por varios elementos: 
+- The flow
+- IOPS (number of input/output operations per second)
+- Block size
+- The sequential or random access model
 
-- Tasa de bits.
-- Las IOPS (o número de operaciones de entrada-salida por segundo).
-- El tamaño de bloque.
-- El modelo de acceso secuencial o aleatorio.
+To date, Enterprise File Storage provides and guarantees performance targets of **64 MB/s per TB and 4000 IOPS per TB**. As a result, the provisioned capacity of the services has a direct impact on the performance available for your service.
 
-A día de hoy, Enterprise File Storage proporciona y garantiza objetivos de rendimiento de **64 MB/s por TB y 4000 IOPS por TB**. La capacidad aprovisionada de los servicios tiene, por tanto, un impacto directo en el rendimiento disponible para su servicio.
+This information is important when you design your storage architecture. Let’s take three examples to illustrate it:
 
-Esta información es importante al diseñar la arquitectura de almacenamiento. Veamos tres ejemplos:
+- **Example 1**: Your application needs a theoretical bandwidth of about **430 MB/s**. To do this, you need to provision at least **7 TB** of storage. Indeed, a quick calculation (**430/64 = 6.72**) allows to estimate the minimum capacity needed to achieve this flow.
 
-- **Ejemplo n°1**: su aplicación necesita una tasa de transferencia teórica de aproximadamente **430 MB/s**. Para ello, debe aprovisionar al menos **7 TB** de almacenamiento. En efecto, un rápido cálculo (**430/64 = 6,72**) permite estimar la capacidad mínima necesaria para alcanzar este caudal.
+- **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
 
-- **Ejemplo n°2**: su infraestructura necesita **4500 IOPS** y un volumen de datos de **1 TB**. Para ello, debe aprovisionar **2 TB** para obtener las **4500 IOPS necesarias**. Más específicamente en este caso, disfrutará de **8000 IOPS** sobre la capacidad aprovisionada. Por lo tanto, el objetivo es recargar el servicio para garantizar el nivel de rendimiento deseado.
+- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
 
-- **Ejemplo n°3**: su aplicación no necesita un rendimiento en particular, pero un volumen de almacenamiento de más de **60 TB**. En ese caso, es preferible optar por el servicio de almacenamiento [NAS-HA](/links/storage/nas-ha), más económico y que permite alcanzar una capacidad superior a 58 TB por servicio.
+### Volumes and quality of services (QoS)
 
-### volúmenes y calidad de servicios (QoS)
+As a reminder, a volume is a partition of the service (also called a pool or a capacity pool). When you place an order, you provision capacity for your service. Once the service has been delivered, you will need to create your volumes, with a quota ranging from 100 GB to 29 TB per volume.
 
-Le recordamos que un volumen es una partición del servicio (también llamada "pool" o "pool de capacidad"). Durante el pedido, aprovecha una capacidad para su servicio. Una vez entregado el servicio, deberá crear sus volúmenes poniendo a su disposición un espacio de entre 100 GB y 29 TB por volumen. 
-
-A continuación ofrecemos la jerarquía de un servicio de almacenamiento Enterprise File Storage:
+Below is the hierarchy for an Enterprise File Storage service:
 
 ![Enterprise File Storage Perf 1](images/Netapp_Hierarchie_2.png){.thumbnail}
 
-Enterprise File Storage todavía no permite cambiar la QoS manualmente. La QoS se define en el nivel de servicio (pool).
+Enterprise File Storage does not yet allow manual modification of the QoS. QoS is defined at the service (pool) level.
+
+### How to maximise file system performance
+
+In order to maximise the performance of your Enterprise File Storage, there are some important considerations:
+
+- Remember to reserve your Enterprise File Storage in the same data centre as your workloads. Latency between data centres can be high and affect your application’s overall performance.
+- For better reliability and maximum bandwidth, favour the latest generation servers as they have the new network interfaces.
+- Identify the public bandwidth available on the client servers, to ensure compatibility with provisioned performance and maximise bandwidth.
+
+### Performance testing
+
+In order to perform your own performance testing and familiarise yourself with Enterprise File Storage service levels, we recommend using tools like [FIO](https://github.com/axboe/fio), a popular assessment tool. It provides many adjustable options to simulate the desired workload and provides detailed statistics on storage behaviour under load. It is also available free of charge on a wide range of operating systems.
 
-### Cómo optimizar el rendimiento de su sistema de archivos
+It is important to test the performance of your Enterprise File Storage in the same data centre as your workloads. Latency between data centres is too high during normal operation for such an assessment to be meaningful.
 
-Para optimizar el rendimiento de su Enterprise File Storage, es importante tener en cuenta:
+Before starting the test, verify that the client used for this benchmark has access to your Enterprise File Storage service and a test volume. If you have not done so yet, you can follow the [managment from OVHCloud Control Panel](/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_control_panel) guide .
 
-- Tenga en cuenta que la solución Enterprise File Storage se reserva en el mismo datacenter que sus cargas de trabajo. La latencia entre los datacenters puede ser elevada y afectar al rendimiento global de su aplicación.
-- Para una mayor fiabilidad y un ancho de banda máximo, favorezca a los servidores de última generación, ya que disponen de las nuevas interfaces de red.
-- Identifique el ancho de banda público disponible en los servidores de clientes para garantizar la compatibilidad con el rendimiento aprovisionado y así maximizar el rendimiento.
+#### Test Bench
 
-### Prueba de rendimiento
+The [FIO](https://github.com/axboe/fio) tool allows you to test several scenarios and modify many test parameters:
 
-Para realizar sus propias pruebas de rendimiento y familiarizarse con los niveles de servicio de Enterprise File Storage, le recomendamos que utilice herramientas como [FIO](https://github.com/axboe/fio), una popular herramienta de evaluación. Ofrece numerosas opciones configurables para simular la carga de trabajo deseada y proporciona estadísticas detalladas sobre el comportamiento del almacenamiento bajo carga. También está disponible de forma gratuita en una amplia gama de sistemas operativos.
+- The number of images
+- Image size
+- Block size
+- The duration of the test
+- The number of FIO workers
+- The access model (read/write/sequential/random), etc.
 
-Es importante probar el rendimiento de su Enterprise File Storage en el mismo datacenter que sus cargas de trabajo. La latencia entre los datacenters es demasiado elevada durante el funcionamiento normal para que dicha evaluación sea pertinente.
 
-Antes de iniciar el test, compruebe que el cliente utilizado para este benchmark tenga acceso a su servicio Enterprise File Storage y a un volumen de prueba. Si todavía no lo ha hecho, puede consultar la guía de [gestión desde el área de cliente de OVHcloud](/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_control_panel).
+Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
 
-#### Banco de pruebas
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
 
-La herramienta [FIO](https://github.com/axboe/fio) le permite probar varios escenarios y modificar numerosos parámetros de prueba: 
+For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
 
-- El número de imágenes.
-- El tamaño de las imágenes.
-- El tamaño de bloque.
-- La duración del test.
-- El número de FIO workers.
-- El modelo de acceso (lectura/escritura/secuencial/aleatoria), etc.
+**You can also use other open-source tools such as:**
 
-Más información sobre [la documentación de FIO](https://fio.readthedocs.io/en/latest/index.html) .
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
 
-## Más información
+## Go further
 
-Si necesita formación o asistencia técnica para implantar nuestras soluciones, póngase en contacto con su representante de ventas o haga clic en [este enlace](/links/professional-services) para obtener un presupuesto y solicitar un análisis personalizado de su proyecto a nuestros expertos del equipo de Servicios Profesionales.
+If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Interactúe con nuestra comunidad de usuarios en Discord : <https://discord.gg/ovhcloud>
+Join our community of Discord users: <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
index 8514108b027..3ecb247cfd7 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
@@ -19,19 +19,19 @@ La notion de « niveau de service » est un élément important dans l’offre E
 - la taille de bloc ;
 - le modèle d’accès séquentiel ou aléatoire.
 
-A ce jour, Enterprise File Storage fournit et garantit des objectifs de performances de **64 Mo/s par To et 4000 IOPS par To**.  Les capacités provisionnées des services ont donc un impact direct sur les performances disponibles pour votre service.
+A ce jour, Enterprise File Storage fournit et garantit des objectifs de performances de **64 MB/s par TB ou 4000 IOPS par TB selon le type d'I/O**.  Les capacités provisionnées des services ont donc un impact direct sur les performances disponibles pour votre service.
 
 Cette information est importante lorsque vous concevez votre architecture de stockage. Prenons trois exemples pour l’illustrer :
 
-- **Exemple n°1** : votre application nécessite un débit théorique d’environ **430 Mo/s**. Pour cela, vous devez provisionner au moins **7 To** de stockage. En effet, un rapide calcul (**430/64 = 6,72**) permet d’estimer la capacité minimale nécessaire pour atteindre ce débit.
+- **Exemple n°1** : votre application nécessite un débit théorique d’environ **430 MB/s**. Pour cela, vous devez provisionner au moins **7 TB** de stockage. En effet, un rapide calcul (**430/64 = 6,72**) permet d’estimer la capacité minimale nécessaire pour atteindre ce débit.
 
-- **Exemple n°2** : votre infrastructure nécessite **4500 IOPS** et un volume de données de **1 To**. Pour cela, vous devez provisionner **2 To** pour obtenir les **4500 IOPS nécessaires**. Plus spécifiquement dans ce cas, vous bénéficierez de **8000 IOPS** sur la capacité provisionnée. Il s’agit donc de sur-provisionner votre service afin d’assurer le niveau de performances souhaité.
+- **Exemple n°2** : votre infrastructure nécessite **4500 IOPS** et un volume de données de **1 TB**. Pour cela, vous devez provisionner **2 TB** pour obtenir les **4500 IOPS nécessaires**. Plus spécifiquement dans ce cas, vous bénéficierez de **8000 IOPS** sur la capacité provisionnée. Il s’agit donc de sur-provisionner votre service afin d’assurer le niveau de performances souhaité.
 
-- **Exemple n°3** : votre application ne nécessite pas de performance en particulier mais un volume de stockage de plus de **60 To**. Dans ce cas, il est préférable de s’orienter vers le service de stockage [NAS-HA](/links/storage/nas-ha), plus économique et permettant d’atteindre des capacités supérieures à 58 To par service.
+- **Exemple n°3** : votre application ne nécessite pas de performance en particulier mais un volume de stockage de plus de **60 TB**. Dans ce cas, il est préférable de s’orienter vers le service de stockage [NAS-HA](/links/storage/nas-ha), plus économique et permettant d’atteindre des capacités supérieures à 58 TB par service.
 
 ### Volumes et qualité de services (QoS)
 
-Pour rappel, un volume est une partition du service (aussi appelée « pool » ou « pool de capacité »). Lors de votre commande, vous provisionnez une capacité pour votre service. Une fois le service livré, vous serez amené à créer vos volumes en mettant à disposition un quota allant de 100 Go à 29 To par volume. 
+Pour rappel, un volume est une partition du service (aussi appelée « pool » ou « pool de capacité »). Lors de votre commande, vous provisionnez une capacité pour votre service. Une fois le service livré, vous serez amené à créer vos volumes en mettant à disposition un quota allant de 100 GB à 29 TB par volume. 
 
 Retrouvez ci-dessous la hiérarchie d’un service de stockage Enterprise File Storage :
 
@@ -66,11 +66,52 @@ L’outil [FIO](https://github.com/axboe/fio) vous permet de tester plusieurs sc
 - le nombre de FIO workers ;
 - le modèle d’accès (lecture/écriture/séquentiel/aléatoire), etc.
 
+Ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteint pour un service EFS de 1TB:
+
+**Lecture aléatoire - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Ecriture aléatoire - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Lecture aléatoire - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Ecriture aléatoire - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+``` 
+**Lecture séquentielle - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+``` 
+**Ecriture séquentielle - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Lecture séquentielle - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+``` 
+**Ecriture séquentielle - Bande passante max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 Retrouvez plus d'informations sur [la documentation de FIO](https://fio.readthedocs.io/en/latest/index.html).
 
+**Vous avez aussi la possibilité d'utiliser d'autres outils open-source comme :**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Aller plus loin
 
 Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services.
 
-Échangez avec notre communauté d’utilisateurs sur Discord : <https://discord.gg/ovhcloud>
 
+Échangez avec notre communauté d’utilisateurs sur Discord : <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
index 64c26161e3a..3ad7218f92c 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
@@ -103,14 +103,11 @@ fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k
 
 Retrouvez plus d'informations sur [la documentation de FIO](https://fio.readthedocs.io/en/latest/index.html).
 
-#### Vous avez aussi la possibilité d'utiliser d'autres outils open-source comme :
-
-> nfsiostat (https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
-
-> NFStest (https://wiki.linux-nfs.org/wiki/index.php/NFStest)
-
-> nfstrace (https://github.com/epam/nfstrace)
+**Vous avez aussi la possibilité d'utiliser d'autres outils open-source comme :**
 
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
 
 ## Aller plus loin
 

From 85163aba483d327894c6ec52b3e2853603881569 Mon Sep 17 00:00:00 2001
From: Yoann Cosse <yoann.cosse@ovhcloud.com>
Date: Fri, 12 Sep 2025 17:32:32 +0200
Subject: [PATCH 4/5] FR-EN duplication

---
 .../netapp_concepts_performances/guide.en-asia.md               | 2 +-
 .../netapp_concepts_performances/guide.en-au.md                 | 2 +-
 .../netapp_concepts_performances/guide.en-ca.md                 | 2 +-
 .../netapp_concepts_performances/guide.en-ie.md                 | 2 +-
 .../netapp_concepts_performances/guide.en-sg.md                 | 2 +-
 .../netapp_concepts_performances/guide.en-us.md                 | 2 +-
 .../netapp_concepts_performances/guide.fr-ca.md                 | 2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
index a794f50fb9f..fa01ff1c502 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Performance Concepts
 excerpt: "Learn about the concepts of provisioning, tracking, and performance testing for Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
index 3ecb247cfd7..8aa81c944c2 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Enterprise File Storage - Concepts de performances
 excerpt: "Découvrez les concepts liés au provisionnement, au suivi ainsi qu'au test des performances de la solution Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
 ## Objectif

From 5531429f9658fccb49e4ea0b52dc42506228432e Mon Sep 17 00:00:00 2001
From: Yoann Cosse <yoann.cosse@ovhcloud.com>
Date: Fri, 12 Sep 2025 18:00:53 +0200
Subject: [PATCH 5/5] Translations

---
 .../guide.de-de.md                            | 47 ++++++++--
 .../guide.es-es.md                            | 49 +++++++++--
 .../guide.es-us.md                            | 85 +++++++++----------
 .../guide.fr-ca.md                            |  2 +-
 .../guide.fr-fr.md                            |  2 +-
 .../guide.it-it.md                            | 50 +++++++++--
 .../guide.pl-pl.md                            | 47 ++++++++--
 .../guide.pt-pt.md                            | 47 ++++++++--
 .../netapp_concepts_performances/meta.yaml    |  3 +-
 9 files changed, 258 insertions(+), 74 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.de-de.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.de-de.md
index 9493f5b6d14..e815a406389 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.de-de.md
@@ -1,13 +1,9 @@
 ---
 title: Enterprise File Storage - Performance-Konzepte
 excerpt: "Entdecken Sie die Konzepte für die Bereitstellung, Überwachung und den Performance-Test von Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-> [!primary]
-> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite.
->
-
 ## Ziel
 
 Auf dieser Seite finden Sie die Konzepte zur Bereitstellung, Überwachung und Überprüfung der Performance von [Enterprise File Storage](/links/storage/enterprise-file-storage).
@@ -70,8 +66,49 @@ Mit dem Tool [FIO](https://github.com/axboe/fio) können Sie verschiedene Szenar
 - Anzahl der FIO-Worker
 - Zugriffsmodell (Lesen/Schreiben/Sequenziell/Zufällig), etc.
 
+Im Folgenden finden Sie einige Beispiele für fio-Befehle, mit denen Sie bestätigen können, dass die maximale Anzahl an IOPS (4000) oder die maximale Bandbreite (64 MB/s) für einen EFS-Dienst von 1 TB erreicht werden können:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 Weitere Informationen finden Sie in [FIO-Dokumentation](https://fio.readthedocs.io/en/latest/index.html).
 
+**Sie können auch andere Open-Source-Tools verwenden, z. B.:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Weiterführende Informationen
 
 Wenn Sie Schulungen oder technische Unterstützung bei der Implementierung unserer Lösungen benötigen, wenden Sie sich an Ihren Vertriebsmitarbeiter oder klicken Sie auf [diesen Link](/links/professional-services), um einen Kostenvoranschlag zu erhalten und eine persönliche Analyse Ihres Projekts durch unsere Experten des Professional Services Teams anzufordern.
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-es.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-es.md
index 3f6e4c95cab..86a3ae52886 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-es.md
@@ -1,13 +1,9 @@
 ---
 title: Enterprise File Storage - Conceptos de rendimiento
 excerpt: "Descubra los conceptos relacionados con el aprovisionamiento, el seguimiento y la prueba de rendimiento de la solución Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
 ## Objetivo
 
 Descubra los conceptos relacionados con el aprovisionamiento, el seguimiento y la prueba del rendimiento de la solución [Enterprise File Storage](/links/storage/enterprise-file-storage).
@@ -70,7 +66,48 @@ La herramienta [FIO](https://github.com/axboe/fio) le permite probar varios esce
 - El número de FIO workers.
 - El modelo de acceso (lectura/escritura/secuencial/aleatoria), etc.
 
-Más información sobre [la documentación de FIO](https://fio.readthedocs.io/en/latest/index.html) .
+A continuación se muestran algunos ejemplos de comandos FIO que permiten confirmar que se puede alcanzar el número máximo de IOPS (4000) o el ancho de banda máximo (64MB/s) para un servicio EFS de 1 TB:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
+Más información en [la documentación de FIO](https://fio.readthedocs.io/en/latest/index.html).
+
+**También puede utilizar otras herramientas open source como:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
 
 ## Más información
 
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
index bad7143fdd2..86a3ae52886 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.es-us.md
@@ -1,73 +1,72 @@
 ---
 title: Enterprise File Storage - Conceptos de rendimiento
 excerpt: "Descubra los conceptos relacionados con el aprovisionamiento, el seguimiento y la prueba de rendimiento de la solución Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-## Objective
+## Objetivo
 
-Learn about the concepts of provisioning, tracking, and performance testing for [Enterprise File Storage](/links/storage/enterprise-file-storage).
+Descubra los conceptos relacionados con el aprovisionamiento, el seguimiento y la prueba del rendimiento de la solución [Enterprise File Storage](/links/storage/enterprise-file-storage).
 
-## Instructions
+## Procedimiento
 
-### Performance monitoring
+### Seguimiento del rendimiento
 
-The concept of “service level” is an important element in the Enterprise File Storage solution. It defines the levels of performance that can be achieved for each provisioned service. File system performance is typically defined by several elements:
+El concepto de "nivel de servicio" es un elemento importante de la solución Enterprise File Storage. Establece los niveles de rendimiento alcanzables para cada servicio aprovisionado. El rendimiento de un sistema de archivos suele definirse por varios elementos: 
 
-- The flow
-- IOPS (number of input/output operations per second)
-- Block size
-- The sequential or random access model
+- Tasa de bits.
+- Las IOPS (o número de operaciones de entrada-salida por segundo).
+- El tamaño de bloque.
+- El modelo de acceso secuencial o aleatorio.
 
-To date, Enterprise File Storage provides and guarantees performance targets of **64 MB/s per TB and 4000 IOPS per TB**. As a result, the provisioned capacity of the services has a direct impact on the performance available for your service.
+A día de hoy, Enterprise File Storage proporciona y garantiza objetivos de rendimiento de **64 MB/s por TB y 4000 IOPS por TB**. La capacidad aprovisionada de los servicios tiene, por tanto, un impacto directo en el rendimiento disponible para su servicio.
 
-This information is important when you design your storage architecture. Let’s take three examples to illustrate it:
+Esta información es importante al diseñar la arquitectura de almacenamiento. Veamos tres ejemplos:
 
-- **Example 1**: Your application needs a theoretical bandwidth of about **430 MB/s**. To do this, you need to provision at least **7 TB** of storage. Indeed, a quick calculation (**430/64 = 6.72**) allows to estimate the minimum capacity needed to achieve this flow.
+- **Ejemplo n°1**: su aplicación necesita una tasa de transferencia teórica de aproximadamente **430 MB/s**. Para ello, debe aprovisionar al menos **7 TB** de almacenamiento. En efecto, un rápido cálculo (**430/64 = 6,72**) permite estimar la capacidad mínima necesaria para alcanzar este caudal.
 
-- **Example 2**: Your infrastructure requires **4500 IOPS** and a data volume of **1 TB**. To do this, you need to provision **2 TB** to get the **required 4500 IOPS**. Specifically, you will get **8000 IOPS** on provisioned capacity. This involves overprovisioning your service to ensure the level of performance you want.
+- **Ejemplo n°2**: su infraestructura necesita **4500 IOPS** y un volumen de datos de **1 TB**. Para ello, debe aprovisionar **2 TB** para obtener las **4500 IOPS necesarias**. Más específicamente en este caso, disfrutará de **8000 IOPS** sobre la capacidad aprovisionada. Por lo tanto, el objetivo es recargar el servicio para garantizar el nivel de rendimiento deseado.
 
-- **Example 3**: Your application does not require any particular performance but a storage volume of more than **60 TB**. In this case, it is best to switch to the more economical storage service [HA-NAS](/links/storage/nas-ha), which can reach capacities higher than 58 TB per service.
+- **Ejemplo n°3**: su aplicación no necesita un rendimiento en particular, pero un volumen de almacenamiento de más de **60 TB**. En ese caso, es preferible optar por el servicio de almacenamiento [NAS-HA](/links/storage/nas-ha), más económico y que permite alcanzar una capacidad superior a 58 TB por servicio.
 
-### Volumes and quality of services (QoS)
+### volúmenes y calidad de servicios (QoS)
 
-As a reminder, a volume is a partition of the service (also called a pool or a capacity pool). When you place an order, you provision capacity for your service. Once the service has been delivered, you will need to create your volumes, with a quota ranging from 100 GB to 29 TB per volume.
+Le recordamos que un volumen es una partición del servicio (también llamada "pool" o "pool de capacidad"). Durante el pedido, aprovecha una capacidad para su servicio. Una vez entregado el servicio, deberá crear sus volúmenes poniendo a su disposición un espacio de entre 100 GB y 29 TB por volumen. 
 
-Below is the hierarchy for an Enterprise File Storage service:
+A continuación ofrecemos la jerarquía de un servicio de almacenamiento Enterprise File Storage:
 
 ![Enterprise File Storage Perf 1](images/Netapp_Hierarchie_2.png){.thumbnail}
 
-Enterprise File Storage does not yet allow manual modification of the QoS. QoS is defined at the service (pool) level.
+Enterprise File Storage todavía no permite cambiar la QoS manualmente. La QoS se define en el nivel de servicio (pool).
 
-### How to maximise file system performance
+### Cómo optimizar el rendimiento de su sistema de archivos
 
-In order to maximise the performance of your Enterprise File Storage, there are some important considerations:
+Para optimizar el rendimiento de su Enterprise File Storage, es importante tener en cuenta:
 
-- Remember to reserve your Enterprise File Storage in the same data centre as your workloads. Latency between data centres can be high and affect your application’s overall performance.
-- For better reliability and maximum bandwidth, favour the latest generation servers as they have the new network interfaces.
-- Identify the public bandwidth available on the client servers, to ensure compatibility with provisioned performance and maximise bandwidth.
+- Tenga en cuenta que la solución Enterprise File Storage se reserva en el mismo datacenter que sus cargas de trabajo. La latencia entre los datacenters puede ser elevada y afectar al rendimiento global de su aplicación.
+- Para una mayor fiabilidad y un ancho de banda máximo, favorezca a los servidores de última generación, ya que disponen de las nuevas interfaces de red.
+- Identifique el ancho de banda público disponible en los servidores de clientes para garantizar la compatibilidad con el rendimiento aprovisionado y así maximizar el rendimiento.
 
-### Performance testing
+### Prueba de rendimiento
 
-In order to perform your own performance testing and familiarise yourself with Enterprise File Storage service levels, we recommend using tools like [FIO](https://github.com/axboe/fio), a popular assessment tool. It provides many adjustable options to simulate the desired workload and provides detailed statistics on storage behaviour under load. It is also available free of charge on a wide range of operating systems.
+Para realizar sus propias pruebas de rendimiento y familiarizarse con los niveles de servicio de Enterprise File Storage, le recomendamos que utilice herramientas como [FIO](https://github.com/axboe/fio), una popular herramienta de evaluación. Ofrece numerosas opciones configurables para simular la carga de trabajo deseada y proporciona estadísticas detalladas sobre el comportamiento del almacenamiento bajo carga. También está disponible de forma gratuita en una amplia gama de sistemas operativos.
 
-It is important to test the performance of your Enterprise File Storage in the same data centre as your workloads. Latency between data centres is too high during normal operation for such an assessment to be meaningful.
+Es importante probar el rendimiento de su Enterprise File Storage en el mismo datacenter que sus cargas de trabajo. La latencia entre los datacenters es demasiado elevada durante el funcionamiento normal para que dicha evaluación sea pertinente.
 
-Before starting the test, verify that the client used for this benchmark has access to your Enterprise File Storage service and a test volume. If you have not done so yet, you can follow the [managment from OVHCloud Control Panel](/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_control_panel) guide .
+Antes de iniciar el test, compruebe que el cliente utilizado para este benchmark tenga acceso a su servicio Enterprise File Storage y a un volumen de prueba. Si todavía no lo ha hecho, puede consultar la guía de [gestión desde el área de cliente de OVHcloud](/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_control_panel).
 
-#### Test Bench
+#### Banco de pruebas
 
-The [FIO](https://github.com/axboe/fio) tool allows you to test several scenarios and modify many test parameters:
+La herramienta [FIO](https://github.com/axboe/fio) le permite probar varios escenarios y modificar numerosos parámetros de prueba: 
 
-- The number of images
-- Image size
-- Block size
-- The duration of the test
-- The number of FIO workers
-- The access model (read/write/sequential/random), etc.
+- El número de imágenes.
+- El tamaño de las imágenes.
+- El tamaño de bloque.
+- La duración del test.
+- El número de FIO workers.
+- El modelo de acceso (lectura/escritura/secuencial/aleatoria), etc.
 
-
-Below are some examples of fio commands to validate that the maximum number of IOPS (4000) or the maximum bandwidth (64MB/s) can be reached for a 1TB EFS service:
+A continuación se muestran algunos ejemplos de comandos FIO que permiten confirmar que se puede alcanzar el número máximo de IOPS (4000) o el ancho de banda máximo (64MB/s) para un servicio EFS de 1 TB:
 
 **Random read - IOPS max**
 ```
@@ -102,16 +101,16 @@ fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k
 fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
 ```
 
-For more information, see [the FIO documentation](https://fio.readthedocs.io/en/latest/index.html).
+Más información en [la documentación de FIO](https://fio.readthedocs.io/en/latest/index.html).
 
-**You can also use other open-source tools such as:**
+**También puede utilizar otras herramientas open source como:**
 
 - [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
 - [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
 - [nfstrace](https://github.com/epam/nfstrace)
 
-## Go further
+## Más información
 
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
+Si necesita formación o asistencia técnica para implantar nuestras soluciones, póngase en contacto con su representante de ventas o haga clic en [este enlace](/links/professional-services) para obtener un presupuesto y solicitar un análisis personalizado de su proyecto a nuestros expertos del equipo de Servicios Profesionales.
 
-Join our community of Discord users: <https://discord.gg/ovhcloud>
+Interactúe con nuestra comunidad de usuarios en Discord : <https://discord.gg/ovhcloud>
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
index 8aa81c944c2..bcbc6590e1b 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-ca.md
@@ -66,7 +66,7 @@ L’outil [FIO](https://github.com/axboe/fio) vous permet de tester plusieurs sc
 - le nombre de FIO workers ;
 - le modèle d’accès (lecture/écriture/séquentiel/aléatoire), etc.
 
-Ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteint pour un service EFS de 1TB:
+Retrouvez ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteints pour un service EFS de 1TB :
 
 **Lecture aléatoire - IOPS max**
 ```
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
index 3ad7218f92c..1caaf5efb60 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.fr-fr.md
@@ -66,7 +66,7 @@ L’outil [FIO](https://github.com/axboe/fio) vous permet de tester plusieurs sc
 - le nombre de FIO workers ;
 - le modèle d’accès (lecture/écriture/séquentiel/aléatoire), etc.
 
-Ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteint pour un service EFS de 1TB:
+Retrouvez ci-dessous quelques exemples de commandes fio permettant de valider que le nombre d'IOPS maximum (4000) ou la bande passante maximale (64MB/s) peuvent être atteints pour un service EFS de 1TB :
 
 **Lecture aléatoire - IOPS max**
 ```
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.it-it.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.it-it.md
index 3c43ddb5513..5ee6a346044 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.it-it.md
@@ -1,14 +1,9 @@
 ---
 title: Enterprise File Storage - Concetti di performance
 excerpt: "Scopri i concetti di approvvigionamento, monitoraggio e test delle performance della soluzione Enterprise File Storage"
-sezione: Enterprise File Storage
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-> [!primary]
-> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina.
->
-
 ## Obiettivo
 
 Scopri i concetti di approvvigionamento, monitoraggio e test delle performance della soluzione [Enterprise File Storage](/links/storage/enterprise-file-storage).
@@ -71,7 +66,48 @@ Il tool [FIO](https://github.com/axboe/fio) ti permette di testare diversi scena
 - Il numero di FIO workers.
 - Il modello di accesso (lettura/scrittura/sequenziale/casuale), ecc...
 
-Per maggiori informazioni, consulta la [documentazione di FIO](https://fio.readthedocs.io/en/latest/index.html).
+Ecco alcuni esempi di comandi fio che permettono di confermare che il numero massimo di IOPS (4000) o la banda passante massima (64 MB/s) possono essere raggiunti per un servizio EFS da 1TB:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
+Per maggiori informazioni consulta la [documentazione FIO](https://fio.readthedocs.io/en/latest/index.html).
+
+**È possibile utilizzare altri strumenti open source, ad esempio:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
 
 ## Per saperne di più
 
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pl-pl.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pl-pl.md
index 8d9f5ae1a88..c309ee98f27 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pl-pl.md
@@ -1,13 +1,9 @@
 ---
 title: Enterprise File Storage - Koncepcje wydajności
 excerpt: "Poznaj koncepcje związane z tworzeniem rezerw, monitoringiem oraz testowaniem wydajności rozwiązania Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-> [!primary]
-> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłóś propozycję modyfikacji" na tej stronie.
->
-
 ## Wprowadzenie
 
 Poznaj pojęcia związane z tworzeniem rezerw, monitorowaniem oraz testowaniem wydajności rozwiązania [Enterprise File Storage](/links/storage/enterprise-file-storage).
@@ -70,8 +66,49 @@ Narzędzie [FIO](https://github.com/axboe/fio) pozwala na przetestowanie kilku s
 - Liczbę FIO workers.
 - Model dostępu (odczyt/zapis/sekwencyjny/losowy) itp.
 
+Poniżej znajdziesz kilka przykładowych poleceń fio pozwalających na potwierdzenie, że maksymalna liczba IOPS (4000) lub maksymalna przepustowość (64MB/s) mogą zostać osiągnięte dla usługi EFS 1TB:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 Więcej informacji znajduje się na stronie [dokumentacja FIO](https://fio.readthedocs.io/en/latest/index.html).
 
+**Możesz również korzystać z innych narzędzi open-source, takich jak:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Sprawdź również
 
 Jeśli potrzebujesz szkolenia lub pomocy technicznej w celu wdrożenia naszych rozwiązań, skontaktuj się z przedstawicielem handlowym lub kliknij [ten link](/links/professional-services), aby uzyskać wycenę i poprosić o spersonalizowaną analizę projektu od naszych ekspertów z zespołu Professional Services.
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pt-pt.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pt-pt.md
index bce8ee61a50..b6b09878fc5 100644
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/guide.pt-pt.md
@@ -1,13 +1,9 @@
 ---
 title: Enterprise File Storage - Conceitos de performance
 excerpt: "Descubra os conceitos relacionados com o aprovisionamento, o acompanhamento e o teste de desempenho da solução Enterprise File Storage"
-updated: 2022-11-30
+updated: 2025-09-12
 ---
 
-> [!primary]
-> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página.
->
-
 ## Objetivo
 
 Descubra os conceitos relacionados com o aprovisionamento, o acompanhamento e o teste de desempenho da solução [Enterprise File Storage](/links/storage/enterprise-file-storage).
@@ -70,8 +66,49 @@ A ferramenta [FIO](https://github.com/axboe/fio) permite-lhe testar vários cen
 - O número de FIO workers.
 - O modelo de acesso (leitura/escrita/sequencial/aleatório), etc.
 
+Encontre aqui alguns exemplos de comandos fio que permitem validar que o número de IOPS máximo (4000) ou a largura de banda máxima (64MB/s) podem ser alcançados para um serviço EFS de 1TB:
+
+**Random read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=8k -size=1G -time_based -runtime=60 -name=test1 -directory=/share-nfs
+```
+**Random write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=8k -size=1G -time_based -runtime=60 -name=test2 -directory=/share-nfs
+```
+**Random read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=64k -size=1G -time_based -runtime=60 -name=test3 -directory=/share-nfs
+```
+**Random write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=64k -size=1G -time_based -runtime=60 -name=test4 -directory=/share-nfs
+```
+**Sequential read - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=8k -size=1G -time_based -runtime=60 -name=test5 -directory=/share-nfs
+```
+**Sequential write - IOPS max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=8k -size=1G -time_based -runtime=60 -name=test6 -directory=/share-nfs
+```
+**Sequential Read - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=read -bs=64k -size=1G -time_based -runtime=60 -name=test7 -directory=/share-nfs
+```
+**Sequential write - Bandwidth max**
+```
+fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=write -bs=64k -size=1G -time_based -runtime=60 -name=test8 -directory=/share-nfs
+```
+
 Encontre mais informações sobre [a documentação do FIO](https://fio.readthedocs.io/en/latest/index.html).
 
+**Também pode utilizar outras ferramentas open-source, como:**
+
+- [nfsiostat](https://man7.org/linux/man-pages/man8/nfsiostat.8.html)
+- [NFStest](https://wiki.linux-nfs.org/wiki/index.php/NFStest)
+- [nfstrace](https://github.com/epam/nfstrace)
+
 ## Quer saber mais?
 
 Se precisar de formação ou de assistência técnica para implementar as nossas soluções, contacte o seu representante comercial ou clique em [esta ligação](/links/professional-services) para obter um orçamento e solicitar uma análise personalizada do seu projecto aos nossos especialistas da equipa de Serviços Profissionais.
diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/meta.yaml b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/meta.yaml
index 436436e9025..61977590ff6 100755
--- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/meta.yaml
+++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_concepts_performances/meta.yaml
@@ -1,2 +1,3 @@
 id: 981dddc1-b903-4948-8fbe-6220f0a3bdf7
-full_slug: public-cloud-storage-netapp-performances
\ No newline at end of file
+full_slug: public-cloud-storage-netapp-performances
+translation_banner: true
\ No newline at end of file