Hello
I want to start a poll: How much is your system load of NLSU2?
My commute from 2.6 to 4.0. I've watched them grow every day. Is this normal?
How much is your system load?
Moderator: Mattk
-
YJB
- Platinum Boarder
- Posts: 387
- Joined: Thu Feb 19, 2009 5:53 pm
- Location: Venhuizen, Netherlands
- Contact:
Re:How much is your system load?
During the month my load is increasing gradually from 1 - 3.5. (1 hour average) The initial hours after a reboot it goes much higher up to 8.
I guess it all depends on how many sensors (current is 8, will go to 11 later this week), how frequent those sensors are reporting as well as the number of graphs you are keeping current.
I'm also pulling data using the meteolog.cgi interface every 5 minutes, that's 5 queries returning approx 70 rows in total.
I guess it all depends on how many sensors (current is 8, will go to 11 later this week), how frequent those sensors are reporting as well as the number of graphs you are keeping current.
I'm also pulling data using the meteolog.cgi interface every 5 minutes, that's 5 queries returning approx 70 rows in total.
Re:How much is your system load?
Hello
My system has been running for 30 days and 20 hours without a reboot.
I invite just 4 images, and a pair of values. Has anyone ever found out where the load limit of the system?
My system has been running for 30 days and 20 hours without a reboot.
I invite just 4 images, and a pair of values. Has anyone ever found out where the load limit of the system?
Re:How much is your system load?
This is a very good subject. I've been concerned about the maximum-sustained system load the NSLU2 can handle.
I accidentaly found out that it can handle 5-12 loads for a few hours here: Meteohub system load consistently 5-12 for hours **SOLVED**
My 266 MHz NSLU2 is on firmware Version 4.2e. It collects data from six VP2 sensors plus the system load "sensor". It makes 21 graphs -- mostly 1 day graphs every 5 minutes and 7 day graphs every 30 minutes, but also some for 5 minutes, 6 hours and a one year graph. It uploads to WeatherUnderground rapid fire every 2 minutes (I found that the upload frequency definitely affects the load).
The normal, non-recomputing system load ranges (it plots a graph of the system load) from 0.0 to 2.0 at beginning of a month to 0.5 to ~7.0 at the end of the month. A typical recompute will drive the upper end of that range up by 2-4 units. I've tried to limit the median load to under 4.0 at all times.
I do have spontaneous reboots on occasion, but I can't prove that they were caused by excessive loads. I generally will manually force a reboot/recompute every 2 weeks or so as a preventative measure. On stock NSLU2s, frequent reboots are a best practive procedure to maximize read/write speeds and prevent other problems.
My concern is what sustained system load levels can the NSLU2 handle without causing write errors into the thumb drive or possibly overheating the CPU or causing program crashes (spontaneous reboots)? Is there a limit? I normally only upgrade firmware early in the month to avoid causing excessive system loads from an upgrade recompute.
I accidentaly found out that it can handle 5-12 loads for a few hours here: Meteohub system load consistently 5-12 for hours **SOLVED**
My 266 MHz NSLU2 is on firmware Version 4.2e. It collects data from six VP2 sensors plus the system load "sensor". It makes 21 graphs -- mostly 1 day graphs every 5 minutes and 7 day graphs every 30 minutes, but also some for 5 minutes, 6 hours and a one year graph. It uploads to WeatherUnderground rapid fire every 2 minutes (I found that the upload frequency definitely affects the load).
The normal, non-recomputing system load ranges (it plots a graph of the system load) from 0.0 to 2.0 at beginning of a month to 0.5 to ~7.0 at the end of the month. A typical recompute will drive the upper end of that range up by 2-4 units. I've tried to limit the median load to under 4.0 at all times.
I do have spontaneous reboots on occasion, but I can't prove that they were caused by excessive loads. I generally will manually force a reboot/recompute every 2 weeks or so as a preventative measure. On stock NSLU2s, frequent reboots are a best practive procedure to maximize read/write speeds and prevent other problems.
My concern is what sustained system load levels can the NSLU2 handle without causing write errors into the thumb drive or possibly overheating the CPU or causing program crashes (spontaneous reboots)? Is there a limit? I normally only upgrade firmware early in the month to avoid causing excessive system loads from an upgrade recompute.