Rob,
The slowest part in the script is finding a route which uses a certain
gateway, in the obsolete interface check part which leads to the big load at
the end of the run time.
I have a version using a dynamically built interface array created during
obsolete route check.
This array is then used to check for unused IPIP interfaces.
This allowed me to reduce the runtime from 4 minutes with some 50% load (1
full core) to under 1 minute with maximum 35% load.
If it works OK i will publish it soon.
Marius, YO2LOJ
-----Original Message-----
From: Rob Janssen
Sent: Sunday, April 10, 2016 11:55
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] Mikrotik RIPv2 AMPR Gateway Setup Script 1.5
(Please trim inclusions from previous messages)
_______________________________________________
Marius,
Do you have any explanation why the script requires a powerful router?
Is it just the general inefficiency of the MikroTik scripting language
execution, is there some
operation called by the script that takes a lot of CPU, or is there a chance
that by using a
more efficient algorithm (e.g. optimization of the case that nothing changes
for an entry) a
lot of performance could be gained?
I ask this because your approach is of course the easiest to have everything
integrated on a
single router, vs two alternatives that could be considered:
- run a Metarouter which does the multipoint IPIP tunneling and runs
ampr-ripd
- run a Metarouter which runs the python scripts that update the config on
the main router
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net