Hi, this does mean, that the prewarm pool's capacity cannot be reclaimed by other actions should the need arise, right? I think that's problematic if that notion isn't carried through into loadbalancing itself as AFAIK the controller currently does not take the prewarm pool into account at all.
Which kind of a workload pattern would that benefit? Got any benchmark and/or just data showcasing that? Cheers, Markus Am Mo., 30. März 2020 um 10:13 Uhr schrieb 甯尤刚 <ning.youg...@navercorp.com>: > Hi, guys > > I wrote a pr here: https://github.com/apache/openwhisk/pull/4870 > this pr's target: make prewarmedPool as `already consumed memory > resources`, this pr has an benefit that if consider prewarmedPool as > consumed memory resource, can aovid to do much `cold start a container` > when the time of `space is consumed finished` is coming > > Have any suggestion? >