Re: waiting for client write

Jeff, Both tomcat vm and RDS vms have 25Gbps Postgresql Db class is db.r6g.16xlarge Tomcat vm is c5.9xlarge --Ayub On Wed, 9 Jun 2021, 17:47 Ayub Khan, wrote: > attached is the screenshot of RDS performance insights for AWS and it > shows high waiting client writes. The api performance is slo

Re: waiting for client write

On Fri, Jun 11, 2021 at 12:28 PM Ayub Khan wrote: > Vijay, > > Both tomcat and postgresql are on the same region as that of the database > server. It is an RDS so I do not have shell access to it. > > Jeff, > > The tomcat profile is suggesting that it's waiting for a response from the > database

Re: waiting for client write

Ranier, Both production and test vms are running on Ubuntu: the below command when executed from client VM shows that its using PMTU 9001. # tracepath dns-name-of-rds 1?: [LOCALHOST] pmtu 9001 On Wed, Jun 9, 2021 at 5:47 PM Ayub Khan wrote: > attached

Re: waiting for client write

Em sex., 11 de jun. de 2021 às 15:19, Ayub Khan escreveu: > Ranier, > > I verified the link you gave and also checked AWS documentation and found > the exact output as shown in AWS: > > https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html > > [ec2-user ~]$ tracepath amazon.com >

Re: waiting for client write

Ranier, I verified the link you gave and also checked AWS documentation and found the exact output as shown in AWS: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html [ec2-user ~]$ tracepath amazon.com 1?: [LOCALHOST] pmtu 9001 1: ip-xxx-xx-xx-1.us-west-1.compute.interna

Re: waiting for client write

Em sex., 11 de jun. de 2021 às 14:59, Ayub Khan escreveu: > Ranier, > > I tried to VACCUM ANALYZE the tables involved multiple times and also > tried the statistics approach as well > Ayub you can try by the network side: https://stackoverflow.com/questions/50298447/postgres-jdbc-client-getting-

Re: waiting for client write

Ranier, I tried to VACCUM ANALYZE the tables involved multiple times and also tried the statistics approach as well Pavan, I upgraded to 42.2.21 version of jdbc driver and using HikariCp connection pool management 3.1.0 jProfiler shows the threads are stuck with high cpu usage on. org.postgres

Re: waiting for client write

Em sex., 11 de jun. de 2021 às 13:59, Ayub Khan escreveu: > Pavan, > > In jProfiler , I see that most cpu is consumed when the Tomcat thread is > stuck at PgPreparedStatement.execute. I am using version 42.2.16 of JDBC > driver. > > > Ranier, > > EXPLAIN ANALYZE > > SELECT a.menu_item_id, a.menu_

Re: waiting for client write

Pavan, In jProfiler , I see that most cpu is consumed when the Tomcat thread is stuck at PgPreparedStatement.execute. I am using version 42.2.16 of JDBC driver. Ranier, EXPLAIN ANALYZE SELECT a.menu_item_id, a.menu_item_name, a.menu_item_category_id, b.menu_item_category_desc, c.menu_item_vari

Re: waiting for client write

Em sex., 11 de jun. de 2021 às 13:28, Ayub Khan escreveu: > Vijay, > > Both tomcat and postgresql are on the same region as that of the database > server. It is an RDS so I do not have shell access to it. > > Jeff, > > The tomcat profile is suggesting that it's waiting for a response from the > d

Re: waiting for client write

Hi Ayub So, i understand the client are blocked waiting on a write to the database! What does the blocked thread signature say? Are you pre-creating any partitions? Are you experiencing Timed outs?? What is the driver you are using now? If you are using Jdbc, can you update your driver to the

Re: waiting for client write

Vijay, Both tomcat and postgresql are on the same region as that of the database server. It is an RDS so I do not have shell access to it. Jeff, The tomcat profile is suggesting that it's waiting for a response from the database server. Tomcat and RDS are in the same availability region as eu-