User Tools

Site Tools

Networking Benchmarks




  • 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
docs/guide-user/perf_and_log/ · Last modified: 2018/03/03 20:15 by