mirror of
https://github.com/python-telegram-bot/python-telegram-bot.git
synced 2024-12-23 06:50:29 +01:00
10 lines
901 B
ReStructuredText
10 lines
901 B
ReStructuredText
|
.. tip::
|
||
|
|
When making requests to the Bot API in an asynchronous fashion (e.g. via
|
||
|
|
:attr:`block=False <telegram.ext.BaseHandler.block>`, :meth:`Application.create_task <telegram.ext.Application.create_task>`,
|
||
|
|
:meth:`~telegram.ext.ApplicationBuilder.concurrent_updates` or the :class:`~telegram.ext.JobQueue`), it can happen that more requests
|
||
|
|
are being made in parallel than there are connections in the pool.
|
||
|
|
If the number of requests is much higher than the number of connections, even setting
|
||
|
|
:meth:`~telegram.ext.ApplicationBuilder.pool_timeout` to a larger value may not always be enough to prevent pool
|
||
|
|
timeouts.
|
||
|
|
You should therefore set :meth:`~telegram.ext.ApplicationBuilder.concurrent_updates`, :meth:`~telegram.ext.ApplicationBuilder.connection_pool_size` and
|
||
|
|
:meth:`~telegram.ext.ApplicationBuilder.pool_timeout` to values that make sense for your setup.
|