i had similar thing with uwsgi i had to manually change config [uwsgi] chdir=/opt/openwisp2 uid=www-data module=openwisp2.wsgi:application master=True pidfile=/opt/openwisp2/uwsgi.pid socket=/opt/openwisp2/uwsgi.sock processes=12 threads=2 listen=600 harakiri=20 max-requests=5000 vacuum=True enable-threads=True env=HTTPS=on buffer-size=8192 ignore-sigpipe ignore-write-errors disable-write-exception
this is my running config for 500+ devices VPS 8 CPUs 8 GB RAM device monitoring is resource extensive. also take in mind the number of interfaces being monitored. for my case i chose only wan interface to monitor. On Fri, Jan 12, 2024 at 10:50 PM Federico Capoano <f.capo...@openwisp.io> wrote: > You can increase the intervals in the openwisp-config and > openwisp-monitoring configuration files, eg: > > /etc/config/openwisp (for openwisp-config) > /etc/config/openwisp-monitoring (for openwisp-monitoring) > > See config options: > > https://github.com/openwisp/openwisp-config?tab=readme-ov-file#configuration-options > > https://github.com/openwisp/openwrt-openwisp-monitoring?tab=readme-ov-file#configuration-options > > This will reduce the load on the system. > In order to increase capacity, there's also other server side tuning you > can do on the linux system or distribute the load on multiple servers, but > these steps are complex and the exact way to implement them depends on your > infrastructure and deployment specific so I cannot explain it here in > detail. > > Best regards > Federico Capoano > > > On Thu, 11 Jan 2024 at 14:56, Dieter Lubbe <dieterlu...@gmail.com> wrote: > >> I've installed Openwisp as a POC to monitor our OpenWRT devices on our >> network. >> When the device count was less than 100 it ran flawlessly, but ever since >> more devices started auto registering, Redis and UWSGI has started to >> consume all available CPU resources. >> >> Currently I have 708 devices with more being added daily. These devices >> are all on the same L2 network. >> >> Nginx will generate "502 Bad Gateway" errors unless I clear the Redis DB >> and restart the services. >> >> Where can I change the interval that OpenWisp checks in with devices? I >> think this might be the cause of the issue. >> >> Thanks >> Dieter >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OpenWISP" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to openwisp+unsubscr...@googlegroups.com. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/openwisp/d2ffb115-052b-4307-af2e-340a6afd37fdn%40googlegroups.com >> <https://groups.google.com/d/msgid/openwisp/d2ffb115-052b-4307-af2e-340a6afd37fdn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to openwisp+unsubscr...@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/CAAGgX6%2BxWvZ9FooKHcQ%3DAWJ4oPyT6ZFmbzqUN%2BSMmP%3DZhbJJBg%40mail.gmail.com > <https://groups.google.com/d/msgid/openwisp/CAAGgX6%2BxWvZ9FooKHcQ%3DAWJ4oPyT6ZFmbzqUN%2BSMmP%3DZhbJJBg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAKOr0YTHpQEmaq0eyuskxcPjn1N9zpyBZDPoiyafDK%3DG2gSjOA%40mail.gmail.com.
