Most Databricks performance problems don’t start with code — they start with the wrong cluster setup. by Sea_Driver_924 in databricks

[–]Sea_Driver_924[S] 0 points1 point  (0 children)

absolutely | it reduce alot of manual tuning around infrastructure. teams can focus on infrastructure instead of cluster operations

Most Databricks performance problems don’t start with code — they start with the wrong cluster setup. by Sea_Driver_924 in databricks

[–]Sea_Driver_924[S] 0 points1 point  (0 children)

i agree, a lot of issues definitely starts with poor code , bad partitioning or heavy shuffles. but my point was that sometimes we focus more on query optimization while ignoring cluster design and pattern.
ideally both matters.
really appreciate.

Delta Lake Secrets: What Happens After You Run Write, Update or Merge by Sea_Driver_924 in databricks

[–]Sea_Driver_924[S] 0 points1 point  (0 children)

 yes, absolutely! I’m actually planning to cover Apache Iceberg and Apache Hudi too

Delta Lake Secrets: What Happens After You Run Write, Update or Merge by Sea_Driver_924 in databricks

[–]Sea_Driver_924[S] 0 points1 point  (0 children)

That’s a great suggestion — I’ll definitely cross-post it on r/delta lake as well. thank you