Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

boto3 vs redshift_connector#195

Discussion options

We've been using boto3 and the RedshiftDataAPIService to fetch results from Redshift with relatively poor performance. After a long time spent trying to optimize our queries and batch them in different ways, today I just tried using this library instead, and the performance of is significantly better.

Cached queries which otherwise were taking up to 10 seconds to fetch via a combination ofexecute_statement andget_statement_result take under 200 milliseconds.

Any insight into why this is the case?

You must be logged in to vote

Hi@benhubsch , apologies for the late response I missed your thread. This is interesting to hear about the difference in performance you saw with boto3 + redshift-data vs redshift-connector. Unfortunately I am not familiar with the inner workings of boto3 and how it integrates with clients such as Redshift Data API.

While I'm happy to hear redshift-connector is more performant for your workload, I'm sure the boto3 + Redshift Data API teams would be interested in hearing about your experience + details about the type of workload you're running to better understand the performance seen. I'd recommend to reach out to AWS Support who can help you get in touch with the boto3 + Data API teams.

Replies: 1 comment

Comment options

Hi@benhubsch , apologies for the late response I missed your thread. This is interesting to hear about the difference in performance you saw with boto3 + redshift-data vs redshift-connector. Unfortunately I am not familiar with the inner workings of boto3 and how it integrates with clients such as Redshift Data API.

While I'm happy to hear redshift-connector is more performant for your workload, I'm sure the boto3 + Redshift Data API teams would be interested in hearing about your experience + details about the type of workload you're running to better understand the performance seen. I'd recommend to reach out to AWS Support who can help you get in touch with the boto3 + Data API teams.

You must be logged in to vote
0 replies
Answer selected byBrooke-white
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
2 participants
@benhubsch@Brooke-white
[8]ページ先頭
©2009-2025 Movatter.jp