Networking Benchmarks

(However such guides only apply for hardware running the factory firmware, once openwrt or any third-party firmware is installed, the network capabilities will switch to the network stack in openwrt or any third-party firmware used)

  • see wireless.overview for diverse tools available in the OpenWrt package respos; (security is a again different field then benchmarking throughput and latency if you are bored)
  • puppet, etc etc
    • In I noticed “sirq” consuming 99% of the CPU (e.g. Ticket 7356)
    • ksoftirqd is the kernel thread responsible for servicing software IRQs which is the context in which Ethernet frames are processe for the RX path, what this means here is:
    1. you are CPU bound; the hardware might be moving packet faster but software cannot keep up
    2. the NAPI implementation (if existing in the driver) might need some tweaking, in particular I see no likely(__napi_schedule_prep) for instance
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2019/07/09 19:28
  • by tmomas