Optimize performance with caching on Databricks
Reading data from cloud object storage is slower than reading from local disk. Without caching, queries and notebooks that read the same Parquet data files repeatedly fetch them from cloud object storage every time.
Databricks uses disk caching to speed up data reads. When a node fetches a Parquet data file from remote storage, it automatically stores a copy on its local storage in a fast intermediate format. Later reads of the same data run locally and are significantly faster. The cache works for all Parquet data files, including Delta Lake tables.
In SQL warehouses and Databricks Runtime 14.2 and above, the CACHE SELECT command is ignored. An enhanced disk caching algorithm is used instead.
Best practices
The disk cache helps most with workloads that read the same data many times, such as repeated or iterative queries on the same tables. Databricks enables it automatically on worker instance types that support it. To help the disk cache speed up reads, follow these practices:
- Choose a worker instance type that supports disk caching. See Selecting instance types to use disk caching.
- Use the disk cache instead of the Apache Spark cache for repeated reads of Parquet and Delta Lake data. See Compare the disk cache and the Spark cache.
Delta cache renamed to disk cache
Disk caching on Databricks was formerly referred to as the Delta cache and the DBIO cache. Disk caching behavior is a proprietary Databricks feature. This name change seeks to resolve confusion that it was part of the Delta Lake protocol.
Compare the disk cache and the Spark cache
The Databricks disk cache differs from Apache Spark caching. Databricks recommends using automatic disk caching.
The following table summarizes the key differences between disk and Apache Spark caching so that you can choose the best tool for your workflow:
Feature | disk cache | Apache Spark cache |
|---|---|---|
Stored as | Local files on a worker node. | In-memory blocks, but it depends on storage level. |
Applied to | Any Parquet table stored on S3, ABFS, and other file systems. | Any DataFrame or RDD. |
Triggered | Automatically, on the first read (if cache is enabled). | Manually, requires code changes. |
Evaluated | Lazily. | Lazily. |
Availability | Enabled by default on certain node types. You enable or disable it with configuration flags. | Always available. |
Evicted | Automatically in LRU fashion or on any file change, manually when restarting a cluster. | Automatically in LRU fashion, manually with |
Disk cache consistency
The disk cache automatically detects when data files are created, deleted, modified, or overwritten and updates its content accordingly. You can write, modify, and delete table data with no need to explicitly invalidate cached data. Any stale entries are automatically invalidated and evicted from the cache.
Selecting instance types to use disk caching
The recommended (and easiest) way to use disk caching is to choose a worker type with SSD volumes when you configure your cluster. Such workers are enabled and configured for disk caching.
The disk cache is configured to use at most half of the space available on the local SSDs provided with the worker nodes. For configuration options, see Configure the disk cache.
Configure the disk cache
Databricks recommends that you choose cache-accelerated worker instance types for your compute. Such instances are automatically configured optimally for the disk cache.
When a worker is decommissioned, the Spark cache stored on that worker is lost. So if autoscaling is enabled, there is some instability with the cache. Spark would then need to reread missing partitions from source as needed.
Configure disk usage
To configure how the disk cache uses the worker nodes' local storage, specify these Spark configuration settings during cluster creation:
spark.databricks.io.cache.maxDiskUsage: disk space per node reserved for cached data in bytesspark.databricks.io.cache.maxMetaDataCache: disk space per node reserved for cached metadata in bytesspark.databricks.io.cache.compression.enabled: should the cached data be stored in compressed format
Example configuration:
spark.databricks.io.cache.maxDiskUsage 50g
spark.databricks.io.cache.maxMetaDataCache 1g
spark.databricks.io.cache.compression.enabled false
Enable or disable the disk cache
To see the current setting for the disk cache, run:
spark.conf.get("spark.databricks.io.cache.enabled")
To enable and disable the disk cache, run:
spark.conf.set("spark.databricks.io.cache.enabled", "[true | false]")
Disabling the cache does not result in dropping the data that is already in the local storage. Instead, it prevents queries from adding new data to the cache and reading data from the cache.