<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Adding nftables interval sets progressively gets slower and makes the nft CLI less responsive with each added set"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1735#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Adding nftables interval sets progressively gets slower and makes the nft CLI less responsive with each added set"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1735">bug 1735</a>
from <span class="vcard"><a class="email" href="mailto:anton.khazan@gmail.com" title="anton.khazan@gmail.com">anton.khazan@gmail.com</a>
</span></b>
<pre>Update: the author of BanIP (OpenWRT application doing similar tasks with
interval sets) shared their method of populating sets and listing the contents
of a table, which avoids the bug. Attaching their version of the test script
for comparison. Looking at the differences, I'm starting to suspect that some
commands cause nftables to re-process all accumulated sets (which causes spikes
in memory use and reduced responsiveness), and some don't. 'nft list tables'
does, while 'nft list ruleset' doesn't. BanIP method of populating the sets
doesn't, while my method does. I still really don't completely understand why
but this looks like a bug to me.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>