Understanding scaledownPeriod

[tramperdk]

Hi everyone! 👋🏻

We've been utilizing KEDA successfully for a while now, especially for scaling our deployments and enabling scaling to zero.

Recently, I've been delving into implementing the http-add-on. I expected that HTTPScaledObjects would mirror the behavior of ScaledObjects, featuring a target value (trigger result or, in this case, pending requests) and a cooldown period that resets with each trigger result.

However, my initial testing suggests that HTTPScaledObjects doesn't quite work that way. Regardless of the number of requests sent through, it consistently adheres to the scaledownPeriod and scales the deployment down from the moment it scaled up + scaledownPeriod, even if it received a request just a second ago.

Is this the intended behavior? If so, is there a way to configure the resources to match the behavior of ScaledObjects, where the scaledownPeriod resets with every received request?

Additionally, we have customers with burst periods where they will send high volumes of requests per second. I want to ensure that we do not lose requests here via the interceptor.
I assume that if the interceptor is not performing, it will act as a sort of queue, and I'd like to avoid that.

Appreciate any insights or tips you can share! 👍🏻