mik-laj commented on issue #13941:
URL: https://github.com/apache/airflow/issues/13941#issuecomment-769893476
@vikramkoka The last message is a fragment of a conversation with one user
to whom I explained why they needs PGBouncer in Airflow. In the Airflow
documentation, it seems to me that in addition to how ("PgBouncer Setup and
Configuration"), we should also explain why we need it and when we don't need
it, so that the user can consciously decide whether to use PGBouncer. If we
explain how many connections each component uses is the user, then the user can
decide that he does not need PgBouncer at all, since their database can handle
enough open connections.
> It would be great if we could describe **why we need PGBouncer**, the
recommended configuration, and ways to tunning this component.
This is especially helpful when you are using cloud solutions and you are
trying to optimize costs. If you know the size of a database instance, you can
estimate how many open connections it can have, and then tune the rest of the
components to most efficiently from that resource, e.g. configure limits for
autoscaling and others.
I haven't added it to the documentation yet, because I still have to verify
all this information and explain how to configure PGBouncer.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
