Skip to content

docs: Add traffic config ref link #5471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 17, 2025
Merged

docs: Add traffic config ref link #5471

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/source/reference/bentoml/configurations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,8 @@ For more information, see :doc:`/build-with-bentoml/runtime-environment`.
class MyService:
# Service implementation

.. _config-traffic:

``traffic``
^^^^^^^^^^^

Expand Down
2 changes: 1 addition & 1 deletion docs/source/scale-with-bentocloud/scaling/autoscaling.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ You can enhance concurrency management with an external request queue on BentoCl

If you enable ``external_queue`` in the ``@bentoml.service`` decorator, you must specify a ``concurrency`` value.

It's worth noting that when the external queue is enabled, ``max_concurrency`` will no longer take effect because BentoCloud guarantees the Service will never receive more requests simultaneously than the ``concurrency`` setting allows. Therefore, ``max_concurrency`` is never reached.
It's worth noting that when the external queue is enabled, ``max_concurrency`` will no longer take effect because BentoCloud guarantees the Service will never receive more requests simultaneously than the ``concurrency`` setting allows. Therefore, ``max_concurrency`` is never reached. For more information, see available fields in :ref:`config-traffic`.

Autoscaling policies
--------------------
Expand Down