rb230 with 64MB CF and 128MB RAM. Ran fine for a year. Upgraded and BAM, CPU at 100 all day every day. Can a 266 really not handle 3.0? What is so different about 3.0? New features, poor coding?
We upgraded three RB230s. after seeing the terrible results, we downgraded to 2.9.51. CPU levels returned to normal:
Your comments are valued.
better CPU load calculation …
did you notice any performance differences, or just the number changed 
?
we noticed that we could barely log in remotely using winbox. took up to a minute to login. Once in, screens were very slow to update. Opening New Terminal took about 10 seconds as well.
Could this be an incompatable configuration from 2.9.5x? Or is the 230 simple antiquated and a poor choice for a base station by today’s standards? We have a bout 5 230s still in operation. we have been slowly replacing them all with 333 and 532s.
I still wonder though, why such a big difference between the ROS versions
I have noticed the 100% CPU utilization on RB133c clients. If you load only the packages that you need the utilization seems to get better. The routerboards will get sluggish and stop responding to commands. A reboot will take care of the problem for a while.
I have noticed the 100% CPU utilization on RB133c clients. If you load only the packages that you need the utilization seems to get better. The routerboards will get sluggish and stop responding to commands. A reboot will take care of the problem for a while.
Does anyone else find this ridiculous? Professionally speaking, having a customer reboot because it is sluggish or unresponsive would pretty much guarantee me a lost customer.
I never install 3.x on anything less than 200MHz, because of the problems you describe above. But I thought for sure a 266 would do ok. Anyone else have this problem? If this is normal, our overpriced 230 boards will be paperweights with 3.0. Although at the moment 2.9.51 does all we need, I just want to make sure that others are having this problem so I can confirm it, and not think there is something wrong with the routerboards themselves.
Cheers fellas!