Merge pull request #2875 from mulesoft/W-16648686-storeprofile-proper…

…ty-44-dm W-16648686-storeprofile-property-44-dm
mulesoft · Nov 29, 2024 · a8765af · a8765af
2 parents 950b8d2 + f263e67
commit a8765af
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/modules/ROOT/pages/migration-cheat-sheet.adoc b/modules/ROOT/pages/migration-cheat-sheet.adoc
@@ -30,4 +30,4 @@ To help you move from Mule 3 to Mule 4, we built this index to help you find the
 * Migrating custom components: You can use the xref:mule-sdk::index.adoc[Mule SDK] to create your own reusable components
 * Migrating DevKit based components: There's a xref:mule-sdk::dmt.adoc[DevKit Migration Tool] that helps to migrate DevKit projects for Mule 3 into Mule SDK ones.
 * xref:migration-transports.adoc[Transport service overrides]: Covers how to migrate from generic transports.
-
+* xref:mule-high-availability-ha-clusters.adoc#configure-the-performance-profile[]: At a container level, change the property from `mule.clusterPartitioningMode=OPTIMIZE_PERFORMANCE` to `mule.cluster.storeprofile=performance`. At an individual application level, you can configure the store profile for a specific Mule application.