To optimize parallel loads, what compressed data file size is recommended by Snowflake?

Master the SnowPro Advanced Architect Test with flashcards, multiple-choice questions, and detailed explanations. Prepare thoroughly for your certification!

Multiple Choice

To optimize parallel loads, what compressed data file size is recommended by Snowflake?

Explanation:
Maximizing parallel loads relies on having enough independent files for Snowflake to process at the same time. Each file can be loaded by a separate loader thread, so you want enough work units to keep the compute warehouse busy without creating excessive per-file overhead. The recommended compressed file size is 100–250 MB because it strikes a balance: large enough to amortize startup and I/O costs per file, yet small enough to generate many concurrent loaders. If files are too small, overhead dominates and throughput drops; if files are too large, you get fewer parallel tasks and underutilize the warehouse. So aiming for around 100–250 MB compressed per file helps maximize parallelism and overall load performance.

Maximizing parallel loads relies on having enough independent files for Snowflake to process at the same time. Each file can be loaded by a separate loader thread, so you want enough work units to keep the compute warehouse busy without creating excessive per-file overhead. The recommended compressed file size is 100–250 MB because it strikes a balance: large enough to amortize startup and I/O costs per file, yet small enough to generate many concurrent loaders. If files are too small, overhead dominates and throughput drops; if files are too large, you get fewer parallel tasks and underutilize the warehouse. So aiming for around 100–250 MB compressed per file helps maximize parallelism and overall load performance.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy