Skip to content

implemented EvaluateAndAdjustConcurrency metrics decision maker #168

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.

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 3 commits into from
Apr 18, 2024
Merged

Conversation

ShocOne
Copy link
Contributor

@ShocOne ShocOne commented Apr 18, 2024

Change

EvaluateAndAdjustConcurrency evaluates the HTTP response from a server along with the request's response time
and adjusts the concurrency level of the system accordingly. It utilizes three monitoring functions:
MonitorRateLimitHeaders, MonitorServerResponseCodes, and MonitorResponseTimeVariability, each of which
provides feedback on different aspects of the response and system's current state. The function aggregates
feedback from these monitoring functions to make a decision on whether to scale up or scale down the concurrency.

The decision is based on a simple majority of suggestions: if more functions suggest scaling down (return -1),
it scales down; if more suggest scaling up (return 1), it scales up. This method centralizes concurrency control
decision-making, providing a systematic approach to managing request handling capacity based on real-time
operational metrics.

Type of Change

  • Refactor (refactoring code, removing code, changing code structure)

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (readme)
  • I did format my code

@ShocOne ShocOne merged commit 8fb326d into main Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant