> For the complete documentation index, see [llms.txt](https://tumbleds-library.gitbook.io/thetumbleds-library/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tumbleds-library.gitbook.io/thetumbleds-library/chapter-4-load-balancing-algorithm-experimental-verification.md). # Chapter 4 Load Balancing Algorithm - Experimental Verification In this chapter, we will present a series of experimental data to validate the conclusions analyzed in the previous chapters. To reduce the burden of the validation work, we only conduct experiments on the two best combinations to verify the analysis in the previous chapters: * ThresholdShedder + LeastResourceUsageWithWeight * UniformLoadShedder + LeastLongTermMessageRate The experimental process aims to enhance the reliability of the conclusions drawn in the previous analysis. If you are not interested in the experimental details, you may skip this chapter and navigate directly to Chapter 5, which covers the `AvgShedder`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tumbleds-library.gitbook.io/thetumbleds-library/chapter-4-load-balancing-algorithm-experimental-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.