You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when reloading/restarting px, with hundreds of senders and dozens of receivers, each one reads the entire routing table into memory. the load on the system goes very high >100 for a minute or two. This can cause forwarding delays.
otoh, if the configurations are not initiallized, that also causes forwarding delays. anyways... ideal would be to have component restart in small batches over a few minutes to avoid the huge spike in load.
The text was updated successfully, but these errors were encountered:
@junhu3@kurt2x@habilinour .... we've wanted something like this for ages, to stop cpu load spiking through the roof on px restart... this implementation just spreads it out, so it takes... something like 10 minutes to run, instead of launching them all in a few seconds.
Should I just put it in the release? then if you don't like how it works, just don't use 'graceful'...
when reloading/restarting px, with hundreds of senders and dozens of receivers, each one reads the entire routing table into memory. the load on the system goes very high >100 for a minute or two. This can cause forwarding delays.
otoh, if the configurations are not initiallized, that also causes forwarding delays. anyways... ideal would be to have component restart in small batches over a few minutes to avoid the huge spike in load.
The text was updated successfully, but these errors were encountered: