Merge pull request #3468 from ClickHouse/aashishkohli-patch-4

Update network-data-transfer.mdx

Author: Blargian

docs/cloud/manage/network-data-transfer.mdx

@@ -21,14 +21,17 @@ Data transfer charges vary by Cloud Service Provider (CSP) and region.
 Public internet egress pricing is based only on the origin region. 
 Inter-region (or cross-region) pricing depends on both the origin and destination regions.
 
+**Best Practices to minimize Data Transfer Costs**
+
+There are some patterns to keep in mind when ingressing and egressing data to minimize data transfer costs.
+1. When ingressing or egressing data from Clickhouse Cloud, use compression where possible, to minimize the amount of data transferred and the associated cost.
+2. Be aware that when doing an INSERT over the native protocol with non-inlined values (e.g. INSERT INTO [TABLE] FROM INFILE [FILE] FORMAT NATIVE), ClickHouse clients pull metadata from servers to pack the data. If the metadata is larger than the INSERT payload, you might counterintuitively see more egress than there is ingress from the server perspective. If this is unacceptable, consider inlining data with VALUES syntax or using the HTTP protocol.
+
+
 The tables below shows how data transfer charges for egress vary across public internet or cross-region by cloud provider and region.
 
 :::note
 ClickHouse Cloud meters inter-region usage in terms of tiers, Tier 1 through Tier 4, depending on the origin and destination regions. The table below shows the tier for each combination of inter-region data transfer. In the Billing usage screen on ClickHouse Cloud you will see data transfer usage broken out by tiers. 
 :::
 
-:::note
-Be aware that when doing an INSERT over the native protocol with non-inlined values (e.g. INSERT INTO [TABLE] FROM INFILE [FILE] FORMAT NATIVE), ClickHouse clients pull metadata from servers to pack the data. If the metadata is larger than the INSERT payload, you might counterintuitively see more egress than there is ingress from the server perspective. If this is unacceptable, consider inlining data with VALUES syntax or using the HTTP protocol.
-:::
-
 <NetworkPricing/>