Skip to content

Commit f69baa2

Browse files
authored
docs: change default mode in webpage as well
1 parent 2df611f commit f69baa2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/Explore Algorithms/LightGBM/Overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -164,11 +164,11 @@ SynapseML must pass data from Spark partitions to LightGBM native Datasets befor
164164
the actual LightGBM execution code for training and inference. SynapseML has two modes
165165
that control how this data is transferred: *streaming* and *bulk*.
166166
This mode doesn't affect training but can affect memory usage and overall fit/transform time.
167+
By default, SynapseML uses "streaming" mode.
167168

168169
#### Bulk Execution mode
169170
The "Bulk" mode is older and requires accumulating all data in executor memory before creating Datasets. This mode can cause
170171
OOM errors for large data, especially since the data must be accumulated in its original uncompressed double-format size.
171-
For now, "bulk" mode is the default since "streaming" is new, but SynapseML will eventually make streaming the default.
172172

173173
For bulk mode, native LightGBM Datasets can either be created per partition (useSingleDatasetMode=false), or
174174
per executor (useSingleDatasetMode=true). Generally, one Dataset per executor is more efficient since it reduces LightGBM network size and complexity during training or fitting. It also avoids using slow network protocols on partitions
@@ -259,4 +259,4 @@ To use it in scala, you can call setUseBarrierExecutionMode(true), for example:
259259
.setUseBarrierExecutionMode(true)
260260
...
261261
<train classifier>
262-
Note: barrier execution mode can also cause complicated issues, so use it only if needed.
262+
Note: barrier execution mode can also cause complicated issues, so use it only if needed.

0 commit comments

Comments
 (0)