BestHub
Sign in
Tagged articles

Join Performance

9 articles · Page 1 of 1
Lakehouse Research Base
Lakehouse Research Base
Dec 21, 2025 · Databases

StarRocks Join Performance Gap: Paimon/Iceberg vs Internal Tables - Root Causes & Fixes

This article analyzes why StarRocks multi-table joins on Paimon/Iceberg tables remain significantly slower than internal tables even after cache warming, detailing six root causes across storage format, data layout, caching, execution engine, metadata, and version management, plus four optimization strategies to narrow the gap.

Join PerformanceLakehouseOLAP
0 likes · 17 min read
StarRocks Join Performance Gap: Paimon/Iceberg vs Internal Tables - Root Causes & Fixes
Alibaba Cloud Big Data AI Platform
Alibaba Cloud Big Data AI Platform
Jan 9, 2025 · Big Data

How Dynamic Filters Supercharge MaxCompute Joins and Cut CPU by 70%

MaxCompute’s dynamic filter and dynamic partition pruning features dramatically accelerate cross‑period join queries by generating runtime filters that prune irrelevant data before the shuffle, reducing scanned data volume by over 95%, cutting CPU usage by 70% and slashing query latency in large‑scale merchant billing workloads.

Dynamic FilterJoin PerformanceMaxCompute
0 likes · 11 min read
How Dynamic Filters Supercharge MaxCompute Joins and Cut CPU by 70%
Code Ape Tech Column
Code Ape Tech Column
Feb 8, 2021 · Databases

Evaluating the ‘No Join Over Three Tables’ Rule from Alibaba Java Development Manual with MySQL and Oracle Experiments

This article investigates why the Alibaba Java Development Manual advises against joining more than three tables by designing and executing large‑scale MySQL and Oracle experiments, analyzing query performance, indexing effects, and data‑generation scripts to determine the practical limits of multi‑table joins.

Database OptimizationJoin PerformanceMySQL
0 likes · 11 min read
Evaluating the ‘No Join Over Three Tables’ Rule from Alibaba Java Development Manual with MySQL and Oracle Experiments
Architecture Digest
Architecture Digest
Feb 2, 2021 · Databases

Why Alibaba's Java Development Manual Prohibits Joins Over Three Tables – MySQL and Oracle Performance Experiments

The article investigates the Alibaba Java Development Manual's rule against joining more than three tables by designing and executing extensive MySQL and Oracle experiments, generating massive test data, measuring query performance, and concluding that the restriction stems from join scalability limits on large datasets.

Database OptimizationJoin PerformanceMySQL
0 likes · 11 min read
Why Alibaba's Java Development Manual Prohibits Joins Over Three Tables – MySQL and Oracle Performance Experiments
Selected Java Interview Questions
Selected Java Interview Questions
Aug 24, 2020 · Databases

Performance Evaluation of Multi‑Table Joins in MySQL and Oracle with Large Data Sets

This article investigates the practical limits of joining more than three tables in MySQL by designing experiments with up to 1.5 billion rows, comparing indexed and non‑indexed queries, and contrasting the results with Oracle's performance, while providing full SQL scripts for data generation and analysis.

Database OptimizationJoin PerformanceMySQL
0 likes · 11 min read
Performance Evaluation of Multi‑Table Joins in MySQL and Oracle with Large Data Sets
ITPUB
ITPUB
Jun 13, 2020 · Databases

Why Does Alibaba Recommend No More Than Three Table Joins? MySQL vs Oracle Performance Test

The article investigates the Alibaba Java development manual's rule that joins involving more than three tables are prohibited, by designing massive MySQL and Oracle experiments, generating billions of rows, measuring query times, analyzing indexing effects, and concluding that the rule is MySQL‑specific and driven by large‑scale performance limits.

Database OptimizationJoin PerformanceMySQL
0 likes · 11 min read
Why Does Alibaba Recommend No More Than Three Table Joins? MySQL vs Oracle Performance Test
21CTO
21CTO
Dec 12, 2019 · Databases

Why Does Alibaba’s Java Handbook Ban Joins Over Three Tables? A Deep MySQL & Oracle Performance Test

This article investigates the claim from Alibaba's Java Development Manual that joining more than three tables should be avoided, by setting up a MySQL 5.7 environment, generating massive synthetic data, executing multi‑table join queries, analyzing execution times, and comparing the results with Oracle, ultimately revealing the practical limits of MySQL joins on large data sets.

Database OptimizationJoin PerformanceMySQL
0 likes · 12 min read
Why Does Alibaba’s Java Handbook Ban Joins Over Three Tables? A Deep MySQL & Oracle Performance Test