I brought up something similar to this recently. We notice this with VM
metadata and passwords in the code. The virtual router does not properly
clean up after itself, so there are leftover entries that the
update_config.py script must continually update which are no longer
relevant. If you make a
A port forward rule operation spent:
not optimized 5min
optimized 3min
optmized+cProfile8min
top 30 :
Fri Aug 19 11:27:50 2016d:\temp\py_pro.data
614887355 function calls (614884838 primitive calls) in 548.846 seconds
Ordered by: cumulative time
Hi Gust
Are you proposing solution "optimized CsAddress.py in VR" or just
analysis on where time is being spent?
Regards
ilya
On 8/18/16 9:34 PM, Gust wrote:
>
> Hi,all
>
> we constructed a advance network in cloudstack , it work fine early , but
> when I added some VR rules ,it execute slow
Hi,all
we constructed a advance network in cloudstack , it work fine early , but when
I added some VR rules ,it execute slow more and more.
About total 100 rules already exist , I add a port forward rule , it would
execute about 3 minutes , that we changed the agent source set more seconds
Hi,all
we constructed a advance network in cloudstack , it work fine early , but when
I added some VR rules ,it execute slow more and more.
About total 100 rules already exist , I add a port forward rule , it would
execute about 3 minutes , that we changed the agent source set more seconds
