The CPU in an SoC is often licensed as a library. For example, going from 500 MHz to 750 MHz clock with the same CPU core is going to be less than 50% faster, often a lot less. With the computational loads of a VPN, a multi-core CPU becomes even more attractive.īecause there are tasks other than just routing the traffic, the throughput doesn't scale directly with CPU speed. A multi-core CPU lets one work with the traffic, while another can handle the other moment-to-moment demands. As Internet speeds have increased, the ability to do this “effortlessly” with a cheap, single-core CPU has been stressed. For most all-in-one routers, this is a primary bottleneck. , as well as any “unnecessary” functions such as GUI or end-user firmware. It also needs to handle every packet for SQM (smart queue management), as well as other tasks, such as DNS, DHCP, VPN, logging, time keeping. The CPU, in most devices, needs to handle the packet flow, including firewall, connection tracking, and NAT. Some devices have two gigabit-rate internal links, which are sometimes configured for WAN and LAN. One point to remember is that often (2019) this is a single “GMII” connection ( gigabit media-independent interface) that is limited to 1 Gbps, raw, so bonding ports on the switch doesn't overcome this limitation. This is, unfortunately, not visible to most end users. The next bottleneck is the connection between the switch and the CPU. For most users working with a reputable manufacturer, it is sufficient to know that the switch and phys in the device were likely properly matched to the rest of device. A 1000 Mbps phy is not a guarantee that the overall device can achieve gigabit rates. A device with a 100 Mbps phy will be limited to ~95 Mbps throughput. The Ethernet switch usually is limited only by the speed of its “phy”, the portion that connects to an Ethernet cable. Each of those components can impact performance of the device. They often include a CPU, wireless subsystem, and Ethernet switch. For example Are "Snapshot" Devices Supported?Īll-in-one routers generally are built around a System-on-a-Chip (SoC). ![]() ![]() This eliminates the Asus RT-AC58U, RT-ACRH13, and similar.įor many opinions, see the OpenWrt Forum. One should expect that 64 MB RAM will be unsupportable in the near future, as well as support for 8 MB of flash.Ī device with two, “ath10k” radios should have at least 256 MB of RAM for stable operation. Support for either 4 MB of flash or 32 MB of RAM has already been discontinued, due to the size of the Linux kernel and run-time footprint of the third-party software required for a basic, running OpenWrt system. Having less than 128 Mbyte of RAM also imposes limitations, basic network functionality may work however there are reports of memory errors while using opkg and luci among other services which may operate unreliable or in worst case freeze the system. Platforms that have less than 16 Mbyte of flash will have noticeable space constraints. Note that some manufacturers claim “32 mb flash” or the like (small “b”) - this is 32 Mbits, or only 4 MBytes. General recommendations are at least 16 Mbyte of flash and 128 Mbyte of RAM. Please note that the OpenWrt project itself does not endorse any hardware or manufacturer unless there's a public statement, this is solely a list put together by the community. ![]() Really specific per scenario but these are generic recommendations based upon what's considered “reasonable” in terms of reliability and performance. This eliminates the Asus RT-AC58U, RT-ACRH13, and similar. Purchase of a device with less than 16 MB of flash or less than 128 MB or RAM is unwise at this time (2019).Ī device with two, “ath10k” radios should have at least 256 MB of RAM. Users should consider multi-core, ARM-based (or x86_64/AMD64) devices for mid-range and higher applications. The second half of this page (specific device recommendations) is very outdated.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |