Effects of packetloss on the system.



  • I’m starting to notice a bit more packetloss than normal on these scorching hot days.

    However I was not aware but it looks like at as much as 1% packetloss shoots my cpu up 10-20% in utilization.

    It makes sense that it would if I were doing file transfers or under some sort of traffic load but the system is pretty much at idle.

    Anyone have ideas on what im experiencing?  The tech in me wants to throw more cpu at it but I’m trying to be reasonable.



  • Probably not the packetloss increasing CPU usage, but CPU usage creating packetloss. Check your system load. CPU usage should not be so bad as to cause loss in most cases. May want to make sure your CPU is not getting so hot that it’s throttling itself.



  • I doubt whether there’s any real diff in CPU usage, and it would take much more than 10% CPU usage to cause 1% loss. It’d have to be absolutely floored, pegged at 100% CPU, to have 1% loss.

    Which process is using the CPU?



  • That’s what’s so confusing.

    last pid: 25624;  load averages:  0.21,  0.15,  0.09  up 0+02:26:37    20:27:32
    185 processes: 3 running, 162 sleeping, 20 waiting

    Mem: 476M Active, 523M Inact, 447M Wired, 220K Cache, 343M Buf, 2000M Free
    Swap: 8192M Total, 8192M Free

    PID USERNAME  PRI NICE  SIZE    RES STATE  C  TIME    WCPU COMMAND
      11 root      155 ki31    0K    32K CPU0    0 142:08  98.58% [idle{idle: cpu0}]
      11 root      155 ki31    0K    32K RUN    1 139:06  96.39% [idle{idle: cpu1}]
    49207 root        25    0  262M 36704K piperd  1  0:00  1.17% php-fpm: pool nginx (php-fpm)
    37507 unbound    21    0 63840K 42384K kqread  1  1:08  0.00% /usr/local/sbin/unbound -c /var/unbound/
        0 root      -16    -    0K  304K swapin  0  0:34  0.00% [kernel{swapper}]
    91580 clamav      20    0  780M  695M select  1  0:30  0.00% /usr/local/sbin/clamd –config-file=/usr
      12 root      -100    -    0K  320K WAIT    0  0:25  0.00% [intr{irq20: hpet0 fxp}]
        0 root      -92    -    0K  304K -      0  0:20  0.00% [kernel{dummynet}]
    34232 squid      20    0  151M 59696K kqread  0  0:16  0.00% (squid-1) -f /usr/local/etc/squid/squid.
    47124 root        20    0  516M  116M bpf    0  0:06  0.00% /usr/local/bin/snort -R 50491 -D -q –su
      12 root      -60    -    0K  320K WAIT    1  0:05  0.00% [intr{swi4: clock}]
        0 root      -92    -    0K  304K -      0  0:05  0.00% [kernel{em2 que}]
    64640 root        20    0 21036K  4976K select  0  0:04  0.00% /usr/local/sbin/miniupnpd -f /var/etc/mi
        5 root      -16    -    0K    16K pftm    0  0:04  0.00% [pf purge]
    13721 root        20    0 14508K  2312K select  0  0:03  0.00% /usr/sbin/syslogd -s -c -c -l /var/dhcpd
    37507 unbound    20    0 63840K 42384K kqread  1  0:03  0.00% /usr/local/sbin/unbound -c /var/unbound/
    74977 avahi      20    0 27616K  3684K select  1  0:03  0.00% avahi-daemon: running [pfSense.local] (a
    17736 root        20    0 16676K  2264K bpf    1  0:03  0.00% /usr/local/sbin/filterlog -i pflog0 -p /

    Just idling saying that it’s free.
    I did notice every once in a while some kind search command running as root.  I figured it was a cron job for a service.



  • That’s basically idle. Any loss is likely attributable to a problem on your Internet connection. The processes you see coming and going are from updaterrd’s stats gathering.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy