Reply to thread

Message

<blockquote data-quote="velis" data-source="post: 727979" data-attributes="member: 96429">OK, I'm terminating my separate development and using Georgius' filter. This latest filter has excellent properties. CPU usage dropped to ~6% (of one core - 3% CPU as compared to previous reports) and there seems to be no packet dropping. The most what I got was a couple of late frames in half an hour. Edit: one discontinuity in 4+ hoursTo clarify: my version had extremely erratic CPU usage in grabber thread that I was unable to resolve. It was able to take 0% CPU and then jump to &gt;20% for no apparent reason. It even did that when I changed the socket to blocking, which should by definition drop the CPU usage to 0%... The funniest thing was that this CPU usage &quot;dancing around&quot; was very smooth (0% for 30 sec, then gradually rise up to 25% then gradually drop down back to 0% - the entire cycle taking from one to 3 minutes)Top all this off with Georgius' great implementation and I see no further reason to continue on this separate path...Since I *know* the filter *can* take 0% CPU, I will attempt to achieve that on Georgius' version instead of mine.</blockquote>

[QUOTE="velis, post: 727979, member: 96429"] OK, I'm terminating my separate development and using Georgius' filter. This latest filter has excellent properties. CPU usage dropped to ~6% (of one core - 3% CPU as compared to previous reports) and there seems to be no packet dropping. The most what I got was a couple of late frames in half an hour. Edit: one discontinuity in 4+ hours To clarify: my version had extremely erratic CPU usage in grabber thread that I was unable to resolve. It was able to take 0% CPU and then jump to >20% for no apparent reason. It even did that when I changed the socket to blocking, which should by definition drop the CPU usage to 0%... The funniest thing was that this CPU usage "dancing around" was very smooth (0% for 30 sec, then gradually rise up to 25% then gradually drop down back to 0% - the entire cycle taking from one to 3 minutes) Top all this off with Georgius' great implementation and I see no further reason to continue on this separate path... Since I [B]*know*[/B] the filter [B]*can*[/B] take 0% CPU, I will attempt to achieve that on Georgius' version instead of mine. [/QUOTE]

Verification