26
Greetings,
We're facing some operational challenges with our NeDi setup (version 2.2.22) running on a Debian VM.
While the system mostly works, we've encountered issues, especially with the long duration of the discovery process. Notably, for devices NeDi marks as "done already," the process for that decision takes about 8 seconds, which is unusual given our nedi.conf timeout setting of 2 seconds. Reducing this setting to 1 second hasn't helped much; it still takes around 4 seconds.
In comparison, our older NeDi server, which we plan to replace, doesn't have these issues. Its discovery decision time is just 1 second, even with a timeout setting of 5 seconds
Both servers are on the same network and there seems to be no obvious differences in their nedi.conf files that could explain the newer server's slower performance. I'm not a NeDi expert though, so I might be missing something.
Additionally, the issue is unlikely to be related to hardware resources, as the VM hosting the new NeDi server has the same CPU capacity and double the RAM compared to the older one.
Could anyone offer insights or suggestions to improve our NeDi configuration's performance?
Thanks for your help and advice.
Cheers
masterblaster
Recent Posts
