kedacore/keda

selenium-grid-scaler: Add abilty to scale more then the request coming to grid by Percentage

Open

#3,453 opened on Jul 17, 2022

View on GitHubContributor guide
 (2 comments) (3 reactions) (0 assignees)Go (1,457 forks)auto 404
feature-requesthelp wantedstale-bot-ignore

Repository metrics

Stars
 (10,372 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi team, it would be great if the selenium-grid-scaler had the option to scale not only when there is more request than browsers, but also to leave some more browsers up than needed. for example, if there are 20 requests for the browser instead of scaling to 20 It will be great to have the ability to scale 20% more than the requested, in this case, 24. that way I can leave some space between the number of requests and the number of available browsers and be able to take more requests before needing to wait for a pod to come up (which takes some time)

Contributor guide

Research direction
Examine the selenium grid scaler code to understand current scaling logic. Add a configuration option for percentage based over provisioning. Modify the scaling calculation to include a buffer percentage. Ensure backward compatibility by defaulting to 0%.
Tech stack
go
Domain
devops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75