Skip to content

Commit b211e28

Browse files
Merge pull request #278733 from ekote/patch-5
Update apache-spark-performance.md
2 parents 7493d0b + 426fbaf commit b211e28

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/synapse-analytics/spark/apache-spark-performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Spark provides its own native caching mechanisms, which can be used through diff
5757
Spark operates by placing data in memory, so managing memory resources is a key aspect of optimizing the execution of Spark jobs. There are several techniques you can apply to use your cluster's memory efficiently.
5858

5959
* Prefer smaller data partitions and account for data size, types, and distribution in your partitioning strategy.
60-
* In Synapse Spark (Runtime 3.1 or higher), Kryo data serialization is enabled by default Kryo data serialization.
60+
* In Synapse Spark (Runtime 3.1 or higher), **Kryo data serialization is enabled by default Kryo data serialization**.
6161
* You can customize the kryoserializer buffer size using Spark configuration based on your workload requirements:
6262

6363
```scala
@@ -86,8 +86,8 @@ To address 'out of memory' messages, try:
8686

8787
Spark jobs are distributed, so appropriate data serialization is important for the best performance. There are two serialization options for Spark:
8888

89-
* Java serialization is the default.
90-
* Kryo serialization is a newer format and can result in faster and more compact serialization than Java. Kryo requires that you register the classes in your program, and it doesn't yet support all Serializable types.
89+
* Java serialization
90+
* Kryo serialization is the default. It's a newer format and can result in faster and more compact serialization than Java. Kryo requires that you register the classes in your program, and it doesn't yet support all Serializable types.
9191

9292
## Use bucketing
9393

0 commit comments

Comments
 (0)