<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em ter, 17 de set de 2019 às 06:29, Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> By occupation I mean utilization.. Something that I can see that the pgpool<br>
> are with '98% of connections slots in use'. I use the pgpool into a docker<br>
> container, so I like to 'kill' the container when pgpool get 99% of<br>
> utilization, so docker swarm (docker orchestrator) will launch a brand new<br>
> container. When I do this, the vacuum in database nodes are more effective,<br>
> the cache are released, I guarantee that all the requests will be executed<br>
> because it will have free connections to use always. I do this 'kill'<br>
> frequently by crontab, but it consume some host resources that are not so<br>
> good. Basically I need to now if the pgpool has slot to receive more<br>
> connections, if don't, I'll kill the container.<br>
> <br>
> I like to propose the following features to monitoring:<br>
> <br>
> - A metric that calculates the utilization of pgpool, calculating a<br>
> percentage using num_init_children max_pool<br>
<br>
Can be obainted from pcp_proc_info today.<br></blockquote><div><br></div><div>I tried this, but I need to put process by process to monitor all pool. I want a way to get info from all process in just one command, if it's possible...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> and child_max_connections<br>
<br>
It's not available today, not terrybly hard to implement, though.<br></blockquote><div><br></div><div>Nice!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> - A metric that show the query execution time<br>
<br>
It's not available today, not terrybly hard to implement, though.<br></blockquote><div><br></div><div>Nice!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> - A metric that show the 'tps', like in pg_top. So I can monitor how many<br>
> transactions has been executed in the pool to measure the efficiency<br>
<br>
It's not available today. Interesting question is, how do you define<br>
tps (I guess you mean "query per second", rather than "transactions<br>
per second" by tps) as it needs to define a duration of query<br>
execution. "Tps" is essentially:<br>
<br>
number_of_queries_executed / duration<br></blockquote><div><br></div><div>Yes! Exactly this! With this I can monitor the throughput of the pgpool and compare with the nodes. </div><div><br></div><div>How can I help to dev/test this or any other features? I'm really willing to help improve this amazing tool!</div><div><br></div><div>Thanks!</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<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>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Abraços!<br><br>=============================<br>José Roberto Emerich Junior<br>=============================</div></div></div></div></div>