Skip to content

Commit 142310a

Browse files
authored
Fix typo in governor periods description
1 parent 2640487 commit 142310a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/ubuntu/features/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ MySQL Governor allows restricting customers that use too many resources. It supp
4141
| READ | bytes | bytes read. Cached reads are not counted, only those that were actually read from disk will be counted |
4242
| WRITE | bytes | bytes written. Cached writes are not counted, only once data is written to disk, it is counted |
4343

44-
You can set different limits for different periods: current, short, med, long. By default those periods are defined as 1 second, 5 seconds, 1 minute and 5 minutes. They can be re-defined using the [configuration file](/cloudlinuxos/cloudlinux_os_components/#configuration-and-operation).
44+
You can set different limits for different periods: current, short, mid, long. By default those periods are defined as 1 second, 5 seconds, 1 minute and 5 minutes. They can be re-defined using the [configuration file](/cloudlinuxos/cloudlinux_os_components/#configuration-and-operation).
4545
The idea is to use larger acceptable values for shorter periods. Like you could allow a customer to use two cores (200%) for one second, but only 1 core (on average) for 1 minute, and only 70% within 5 minutes.
4646
That would make sure that customer can burst for short periods of time.
4747

0 commit comments

Comments
 (0)