Hi Max, Good morning! Thanks so much for your review and feedback!
I agree on proposal being generic and might not benefit a normal user without
having a decent understanding of how autoscaler’s logic works.
I had actually planned to contribute some predictive implementations using the
custom
Thanks a lot for reviewing the FLIP! Absolutely agree with the point of having
some general strategies inside autoscaler itself. cc. @Max since you had
similar thoughts on this, I’d love to get your inputs as well on following :)!
One of the general strategies that could be beneficial to users c
+1.
It's very useful to me.
+1 for this proposal, it allows advanced Users to introduce some specific
strategies.
Also, if some strategies are general enough, it's better to put them inside
the autoscaler.
Best,
Rui
On Sat, Mar 29, 2025 at 3:09 PM wrote:
> Hi Venkata,
>
> Let’s keep this discussion about the FLIP and not
Hi Venkata,
Let’s keep this discussion about the FLIP and not other unrelated topics.
You are welcome to post the question in a new thread .
Thanks
Gyula
Sent from my iPhone
> On 29 Mar 2025, at 02:58, Venkatakrishnan Sowrirajan wrote:
>
> Hi Pradeepta,
>
> Thanks for the nice proposal. I
Hi Pradeepta,
Thanks for the nice proposal. I am curious, how does the current autoscaler
as well as the newly proposed custom evaluator plugin work for batch
execution mode?
Regards
Venkata krishnan
On Thu, Mar 20, 2025 at 11:33 PM Pradeepta Choudhury
wrote:
> Hi Max, Good morning! Thanks so
Hi Gyula, Good morning! Thanks so much for your review and feedback!
I absolutely agree about the problem of identifying a job vertex well enough to
make more informative decisions using the custom evaluator. Would be more than
happy to explore an approach for associating operators with vertex
Hi Pradeepta,
Generally, the proposal looks good to me. The only issue I see is that
it is fairly generic. On the one hand, it allows plugging in
additional evaluation logic into the autoscaler, which allows for many
new ways to extend the current autoscaling logic. On the other hand,
normal users
Hi!
I think this is a very nice proposal, +1 from me!
The only practical challenge is to actually be able to identify what job
vertex is what in the job graph to make good predictions / feed in external
information but this is definitely out of scope here.
The autoscaler in general needs to have
