[ovs-discuss] ovs-vswitchd memory consumption behavior

Ben Pfaff blp at ovn.org
Mon Mar 18 21:37:21 UTC 2019


Did you try compiling with Address Sanitizer yet?  It is just as
effective as valgrind at finding leaks, but it slows the process much
less than valgrind does, so it is less likely to change behavior due to
timing issues.

On Mon, Mar 18, 2019 at 07:36:06AM +0000, Fernando Casas Schössow wrote:
> After two days of running OVS through valgrind again I suspect that for some reason (probably how Valgrind works) the leak is not happening while running through Valgrind.
> 
> Please find attached two sets of valgrind logs in case they can help but I really doubt it.
> 
> As soon as I run OVS alone again, the leak starts and after 5 days it's already using around 360MB as you can see in the chart attached (taked from munin):
> 
> Any other ideas on how I can try to catch the leak are welcome.
> 
> Thanks.
> 
> On dom, mar 10, 2019 at 9:40 AM, Fernando Casas Schössow <casasfernando at outlook.com> wrote:
> Hi Ben,
> 
> I uploaded to the same place a new trace after running OVS through Valgrind for around 5 days.
> 
> The file name is: ovs-valgrind-4-days-run_no_detach_no_monitor.log.gz
> 
> However I have a strong feeling that for some reason the leak is not happening while running OVS through Valgrind. I monitored the rss size of valgrind during these last few days and it remained stable since the beginning (around  144MB) and it didn't increase.
> 
> Having said that I'm giving valgrind one last shot, running the process exactly the same as Alpine service file does, including the --detach and --monitor option but to be honest I don't have too much hope. The command looks like this:
> 
> sudo valgrind --trace-children=yes --leak-check=full --show-leak-kinds=all -v --log-file="ovs-valgrind.%p.log" /usr/sbin/ovs-vswitchd --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor --mlockall unix:/var/run/openvswitch/db.sock
> 
> I will leave it running until Thursday night or so and upload a new set of logs.
> 
> Let me know if the new valgrind log I uploaded was of any help.
> 
> Thanks,
> 
> Fer






More information about the discuss mailing list