Closed csilzen closed 3 years ago
Yeah athena often runs into its own throttling limits. One thing you could try is setting the waitForResults
flag as false in the constructor. This will return the QueryExecutionId
for each query executed in Athena, which will be much faster than waiting for query results. You can then pass this QueryExecutionId back into athena-express after waiting a few arbitrary seconds. The overall time will likely remain the same as before, but you can manage this better and as a bonus - your Lambda costs will be lower as you won't be waiting for queries to finish.
Is there a way to run multiple queries concurrently? I'm working with AWS Lambda and trying to run the following code seems to take exponentially longer than when I was simply using just one latitude/longitude point, so I'm unsure of how else to set it up.