Netduma Cameron

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

I believe this is DHCP requesting an IPv6 address and not getting one.
This is not concerning as long as you can connect to the internet. Your ISP most likely provides IPv4 only.
If you would like support with anything, please create a new thread instead because I most likely will not be able to provide support quickly since I am developing.
Thanks.

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

I believe this is DHCP requesting an IPv6 address and not getting one.
This is not concerning as long as you can connect to the internet. Your ISP most likely provides IPv4 only.
If you would like support with anything, please create a new thread instead because I most likely will not be able to provide support quickly since I am developing.
Thanks.

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

CPU3 is currently removed from the scheduler, so not running any user space code (i.e. rapps). It handles hardware interrupts that need low latency, for example from Wi-Fi and Ethernet devices. I've experimented with enabling it in user space but it will most likely need to be reserved to keep the connection as fast, reliable and stable as possible.
Here's a screenshot of my CPU usage while i do a 1Gbit download, with CPU3 active:

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!