Skip to content

Commit

Permalink
Some minor updates.
Browse files Browse the repository at this point in the history
Signed-off-by: Santiago Pericas-Geertsen <[email protected]>
  • Loading branch information
spericas committed Feb 4, 2025
1 parent 64b0f10 commit 308525c
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 5 deletions.
16 changes: 11 additions & 5 deletions docs/src/main/asciidoc/se/guides/performance-limits.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ it may be beneficial
to limit the number of concurrent requests accepted by the Helidon webserver in
order to improve the overall experience. When doing so, it should also be possible
to establish rules for those requests that cannot be serviced immediately,
as well as how grow or shrink the number of _permits_ available in the system.
as well as how to grow or shrink the number of _permits_ available in the system.
== Setting Concurrency Limits
Expand Down Expand Up @@ -71,7 +71,12 @@ will be queued, if possible, and any request that sits in the queue for more tha
Instead of fixing the number of permits to a given value, the AIMD strategy
allows the set of permits to grow arithmetically and shrink multiplicatively
as needed. For example,
as needed, based on the actual time that it takes to process requests. AIMD
can dynamically adjust the number of available permits to ensure a certain
_quality of service_, possibly for a subset of all the requests received.
It is generally preferred to serve a subset of clients efficiently than
all clients inefficiently, and this type of tradeoff can be defined using
an AIMD strategy. For example,
[source,yaml]
----
Expand Down Expand Up @@ -131,8 +136,8 @@ strategies see:
== Metrics
The Concurrency Limit module also has built-in support for metrics in order
to monitor a certain strategy. These metrics are disabled
by default, but can be enabled as follows:
to monitor the chosen strategy. These metrics are disabled by default,
but can be enabled as follows:
[source,yaml]
----
Expand All @@ -150,7 +155,8 @@ server:
The following tables describe the metrics that are available for each of the
strategies described above. A metric tag `socketName=<name-of-socket>` is used to
group metrics that correspond to a particular socket; for simplicity this metric tag
is _omitted_ for the default socket.
is _omitted_ for the default socket. All metrics provided by the Concurrency Limit
module are in **vendor** scope.
.Fixed
|===
Expand Down
1 change: 1 addition & 0 deletions docs/src/main/asciidoc/sitegen.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -331,6 +331,7 @@ backend:
- "webclient.adoc"
- "dbclient.adoc"
- "performance-tuning.adoc"
- "performance-limits.adoc"
- type: "MENU"
title: "Config"
dir: "config"
Expand Down

0 comments on commit 308525c

Please sign in to comment.