Status: Waiting on AWS
-
Local DB psql:
❰master_user@local_integration❱ =# select(now()); ┌───────────────────────────────┐ │ now │ ├───────────────────────────────┤ │ 2016-08-30 22:47:55.094061+00 │ └───────────────────────────────┘ (1 row) Time: 0.390 ms
AWS DB psql:
❰master_user@aws_integration❱ => select(now()); ┌───────────────────────────────┐ │ now │ ├───────────────────────────────┤ │ 2016-08-30 22:52:03.780157+00 │ └───────────────────────────────┘ (1 row) Time: 52.992 ms
Don't worry though guys, everything is good:
What good's a dashboard if it doesn't tell the truth?
-
Does the 52ms include the round trip from one computer to the other?
-
Also relevant, beginning to see recovery = /= recovered
-
@Matches said in Status: Waiting on AWS:
Also relevant, beginning to see recovery = /= recovered
Except that the text only discusses the time to modify or create instances, not get data in or out.
-
@ben_lubar said in Status: Waiting on AWS:
Does the 52ms include the round trip from one computer to the other?
Probably, but integration tests running in the same AZ and (probably VPC) are taking 30x longer as well.
-
Amazon should really just stop all the instances that are being abused to DDOS attack people.
-
I thought we're supposed to be using serverless setups now? what is this talk about instances and load??
-
@bb36e Unfortunately technology hasn't advanced that far, we have to have websocket interchanges serverside for now.