We have been running a 72 AP, 2 PoE Switch, ER8411 Router with an Omada Software Controller on a custom built 1U linux embeddded low power Hardware. We see that the controller software uses about 2.18 GB RAM + another 44 MB for mongo DB. The board cann support only 4 GB RAM max and that much is installed. The CPU is Intel Atom D2500, 2C2T, 1.866GHz
 

Our current, configuration of omadaDOTproperties is as under:

max DOT device=150

And the following has been added to control.sh:

-Xms1024m -Xmx1024m

Are these numbers reasonable and to be expected for such a system. Is their a way to reduce the memory footprint of Omada by tweaking some other startup parameter ?

Also we observed that:

(1) On startup, Omada takes long time to start. Once startup is completed, the Omada Software's CPU usage stays at 100% for a good amount of time (5+ minutes), but after that falls to 5%. Is this behavior to be expected ?

(2) Whenever a configuration is made from mobile app or Web-interface of omada.tplinkcloud.com that impacts all APs, then the CPU shoots momemntarily to 100% but this is for very small duration of time. The problem is that after this few APs go into a flapping state of ADOPTING & DOSCONNECTED. The APs have to be recovered either by Force Provisioning (sometime even this does not work) or Rebooting by "PoE recovery". This problem usually does not happen if the configuration is done directly from webinterface of controller hardware (Controller-IP COLON 8043)