forked from TrueCloudLab/frostfs-qos
No description
Let's assume that for some tag `limit = 1000 RPS` defined and each request takes 10 ms to complete. At some point in time 1000 requests were accepted. Then first request will be scheduled at `now()`, second - at `now() + 1 ms`, third - at `now() + 2 ms` etc. Total processing duration of 1000 requests will be 1 second + 10 ms. After this fix scheduler looks forward to schedule requests within limit. So for situation above total processing duration of 1000 requests will be 10 ms in ideal world. The same for reservation scheduling. Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com> |
||
---|---|---|
.forgejo | ||
internal/assert | ||
limiting | ||
scheduling | ||
tagging | ||
.gitattributes | ||
.gitignore | ||
.golangci.yml | ||
.pre-commit-config.yaml | ||
CODEOWNERS | ||
go.mod | ||
go.sum | ||
LICENSE | ||
Makefile | ||
README.md |
Quality of Service (QoS) Go libraries for FrostFS object storage
See package documentation at pkg.go.dev
License and copyright
Copyright 2023-2025 FrostFS contributors
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.