<HTML><BODY>
Thanks for your answer. We have to test it on some test environment first as the production is used. Perhaps not a good idea to go with a beta for prod. <div>Any idea how to optimize the 3.4.3 with settings so it performs better with the extended protocol?<br><br><br><br>
>-------- Оригинално писмо --------
<br> >От: Tatsuo Ishii ishii@postgresql.org
<br> >Относно: Re: [pgpool-general: 4300] Very slow write performance on write
queries only
<br> >До: therat@abv.bg
<br> >Изпратено на: 08.01.2016 00:52
<br><br>Assuming that you do not run out CPU on the machine where pgpool is<br>
running on, extended protocol (which is mainly used in Java<br>
applications) is slow with pgpool-II. Upcoming 3.5 will enhance this<br>
area. The 3.5 beta is already out, and you could try it out if you<br>
like.<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" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
> Hello, <br>
> We're experiencing very slow write performance while using pgpool with 3 backend postgres nodes. We noticed it now that we have an import job running trough tomcat that imports millions of rows in the database using insert and update statements. <br>
> When running without pgpool the time for completion of the import is literally 10 times less. (e.g 20 minutes instead of more than 3 hours). I know there is some overhead, but it's cited to be around 20%. <br>
> Could someone please assist in tuning the write performance of the installation. <br>
> Latest stable version of pgpool 3.4.3-1 <br>
> Here is the config: <br>
[snip because of a too long line]<br>
</div></BODY></HTML>