最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

aws lambda - Why does one S3-to-Redshift COPY operation take 50+ seconds while seven identical operations take 2-3 seconds? - St

programmeradmin0浏览0评论

A lambda that DELETEs and COPYs 8 parquet files from S3 into 8 Redshift tables (using boto3).

Each table is created from a single file, each with less than 3K rows.

7 of the queries take 2-3 seconds each, and one takes 50+ seconds.

I have exhausted my checks and not sure what this can be, this didn't work:

  • Removed all fks/constraints
  • VACUUM/ANALYZE the tables
  • Recreated the tables
  • Changed the isolation levels
  • Increased the Lambda memory/CPU allocation

Notable considerations:

  • When I run it directly on Redshift (not the datashare), the COPY takes 2s.
  • It's definitely the COPY and not the DELETE (confirmed via logging).

Any suggestions appreciated!

与本文相关的文章

发布评论

评论列表(0)

  1. 暂无评论