Redshift requests are 10x slower when using the console compared to calling them from Java code

We use Java code to access the Amazon Redshift database (from an EC2 instance or local machine) and everything works fine, but when we connect to any other client on our laptops, it is 10x or more slower. We are based in Europe and Redshift is located in the Amazon Oregon datacenter.

  • All types of requests are affected
  • It doesn't matter which client we are using (psql, SQL Workbench ..) except directly from the code

Could this be related to SSL or smth encryption at the network layer?

If you need more data, please ask.

The same question was asked for Amazon support, they said they fixed it and after a week it was back to normal. This is obviously a general problem, but it has nothing to do with network latency. Is there any way to avoid this. How do you access your production data?

+3


source to share


1 answer


Everyone faces the same problem: you are not the first. The problem is network latency. It's funny, but Redshift calculates the execution time of the request to the last line accepted by your client. Just let it go.



0


source







All Articles