← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Jun 4, 2026

Improved workspace file write performance on classic compute

Workspace file operations on classic compute now use asynchronous flushing by default for Databricks Runtime 17.1 and above.

What it does

Workspace file operations on classic compute now use asynchronous flushing by default for Databricks Runtime 17.1 and above. File writes, deletes, and metadata operations are batched and flushed in the background, reducing latency for workloads that write many files, such as Git operations. Workspace files are the files stored and managed in the Databricks workspace file system.

Why it matters

File writes, deletes, and metadata operations are batched and flushed in the background, reducing latency for workloads that write many files, such as Git operations.

Architecture
Databricks Platform → Platform
In short

Workspace file operations on classic compute now use asynchronous flushing by default for Databricks Runtime 17.1 and above. File writes, deletes, and metadata operations are batched and flushed in the background, reducing latency for workloads that write…

Read the full documentation ↗
Key takeaway
Workspace file operations on classic compute now use asynchronous flushing by default for Databricks Runtime 17.1 and above.
2026-06-04-improved-workspace-file-write-performance-on-classic-compute Generated by the Databricks Updates Agent · browse all updates