<div dir="rtl"><div style="" dir="ltr">The load average was pretty normal in both cases so I dont think that limited resources are the root cause here. 40% performance loss is pretty big number, isnt there a way to debug it ?</div></div><br><div class="gmail_quote"><div dir="rtl">בתאריך יום א׳, 23 בדצמ׳ 2018 ב-13:49 מאת Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Pgpool-II needs to store and forward each network packet from clients<br>
and PostgreSQL. So usually about 40% performance loss is expected<br>
comparing with direct connecting to PostgreSQL. That says, if your<br>
application's SELECT reads a lot of rows for example, it may take more<br>
time.<br>
<br>
Another point of consideration is, hardware resources especially CPU,<br>
memory and network. In your test case #1, on node A only applications<br>
and walreciver use CPU, On the other hand in test case #2, on node A<br>
the applications, Pgpool-II and walreciver use CPU. So it maybe<br>
possible Pgpool-II cannot get enough CPU. Have you checked resource<br>
usage?<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
> I meant that max_connection is set to 500. I did the same text with<br>
> num_init_children=500 but same performance(because my app doesnt use in<br>
> this architecture more then 200 connections..).<br>
> <br>
> בתאריך יום א׳, 23 בדצמ׳ 2018 ב-10:29 מאת Pierre Timmermans <<br>
> <a href="mailto:ptim007@yahoo.com" target="_blank">ptim007@yahoo.com</a>>:<br>
> <br>
>> What do you mean by "My db has 500 max connections" ? If you have 500<br>
>> concurrent connections, then you should set num_init_children to 500,<br>
>> because now you can have no more than 200 concurrent users (with pgpool a<br>
>> connection is released from the pgpool only if it the session disconnects<br>
>> from postgres)<br>
>><br>
>> Pierre<br>
>><br>
>><br>
>> On Sunday, December 23, 2018, 9:26:17 AM GMT+1, Mariel Cherkassky <<br>
>> <a href="mailto:mariel.cherkassky@gmail.com" target="_blank">mariel.cherkassky@gmail.com</a>> wrote:<br>
>><br>
>><br>
>> Hi,<br>
>> I'm using pgpool and I'm suffering from very poor performance issues when<br>
>> using the pool. I have the next architecture :<br>
>> 1)Node A, contains the application,standby database and pgpool service.<br>
>> 2)Node B contains the primary db and pgpool service that will be used only<br>
>> in failover.<br>
>><br>
>> I did the next 2 tests :<br>
>> -In the first test, the application on node A access the DB on node B<br>
>> directly, without connecting to the pool. I run one of our application`s<br>
>> major procedures and it took 40s.<br>
>> -In the second test, the application on node A access the pool on node A<br>
>> and it redirects the queries to node B. I run the same procedure and it<br>
>> took 3minutes.<br>
>><br>
>> My db has 500 max connections and the application has only 1 user and 1 db<br>
>> so I set the num_init_children to be 200 and pool_size to be 1.<br>
>><br>
>> Any idea how can I tune the pgpool ?<br>
>><br>
>> Thanks.<br>
>> _______________________________________________<br>
>> pgpool-general mailing list<br>
>> <a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
>> <a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
>><br>
</blockquote></div>