---
title: "Discussion on \"How Z-Order Cut My Databricks ETL Time in Half\" | Hashnode"
description: "Discussion on \"How Z-Order Cut My Databricks ETL Time in Half\". Z-Order cut my Databricks ETL from 1m40s to 50s per tenant. Here's why partitioning failed and how Z-Order works like a clustered index for Delta Lake."
url: "https://hashnode.com/posts/how-z-order-cut-my-databricks-etl-time-in-half/6995f5bd76926e7d4ed2c776"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How Z-Order Cut My Databricks ETL Time in Half](https://arnaudp.dev/how-z-order-cut-my-databricks-etl-time-in-half?utm_source=hashnode&utm_medium=feed)

Z-Order cut my Databricks ETL from 1m40s to 50s per tenant. Here's why partitioning failed and how Z-Order works like a clustered index for Delta Lake.

Feb 18 · 7 min read · arnaudp.dev  
Read the article

-   [#data-engineering](https://hashnode.com/tag/data-engineering)
-   [#data-optimization](https://hashnode.com/tag/data-optimization)
-   [#databricks](https://hashnode.com/tag/databricks)
-   [#delta-lake](https://hashnode.com/tag/delta-lake)
-   [#sql](https://hashnode.com/tag/sql)

## Written by

[Arnaud Pouppeville](https://hashnode.com/@apouppeville)

@apouppeville

  
[View profile](https://hashnode.com/@apouppeville)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
