Hi there,
We are testing a new application to try to find performance issues.
AWS RDS m4.large 500GB storage (SSD)
One table only, called Messages:
Uuid
Country (ISO)
Role (Text)
User id (Text)
GroupId (integer)
Channel (text)
Title (Text)
Payload (JSON, up to 20kb)
Starts_in (UTC)
Expires_in
Are the inserts being done through one connection or multiple connections
concurrently?
Sent from my iPhone
> On Dec 24, 2017, at 2:51 PM, Jean Baro wrote:
>
> Hi there,
>
> We are testing a new application to try to find performance issues.
>
> AWS RDS m4.large 500GB storage (SSD)
>
> One
Multiple connections, but we are going to test it with only one. Would it
make any difference?
Thanks
Em 24 de dez de 2017 21:52, "michael...@sqlexec.com"
escreveu:
> Are the inserts being done through one connection or multiple connections
> concurrently?
>
> Sent from my iPhone
>
> > On Dec
Yes it would/does make a difference! When you do it with one connection
you should see a big performance gain. Delayed, granted, extend locks
(locktype=extend) can happen due to many concurrent connections trying
to insert into the same table at the same time. Each insert request
results in a
I had an opportunity to perform insertion of 700MM rows into Aurora
Postgresql, for which performance insights are available. Turns out, that
there are two stages of insert slowdown - first happens when max WAL
buffers limit reached, second happens around 1 hour after.
The first stage cuts insert
Thanks for the clarification guys.
It will be super useful. After trying this I'll post the results!
Merry Christmas!
Em 25 de dez de 2017 00:59, "Danylo Hlynskyi"
escreveu:
> I had an opportunity to perform insertion of 700MM rows into Aurora
> Postgresql, for which performance insights are a