Small files in S3 cause Redshift COPY slowdowns (each file triggers a slice). Solutions: (1) Coalesce before load—run a Spark/Glue job to merge files (e.g., 128MB per file). (2) Use manifest files—COPY from a manifest listing fewer, larger files. (3) Enable MANIFEST in Glue/ETL to output fewer parts. (4) Buffer in Kinesis Firehose with size/count thresholds. (5) Use Redshift Spectrum for ad-hoc S3 queries without loading. Best practice: target 1–128MB files per Redshift slice....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Capco. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.