Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    35-45% cpu initization in testing lab

    Scheduled Pinned Locked Moved Hardware
    14 Posts 4 Posters 5.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      eyepodder
      last edited by

      I replaced the HD and the CPU % has dropped down to 5-7% from 35-45%. I guess a bad HD increases CPU load quite a bit. LOL ::)

      What's wrong with the Dlink card? It's a 1 Gig card. I was going to replace the LAN and DMZ cards with them as I was planning of having a webserver (fronted)in the DMZ and a MySql server in the LAN side for protection so I figured that faster cards between to DMZ and LAN would be better and stick with the 3com and the WAN side.

      1 Reply Last reply Reply Quote 0
      • P
        Perry
        last edited by

        Intel and 3com should in general have better written drivers for Freebsd, by that means lower cpu usages. So it could be worth a test imo.

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • E
          eyepodder
          last edited by

          It's back up to 35%-40%. When I did a top -S I see that syslogd hovering around 17-18% and the STATE is SELECT.

          Why is syslogd so high is that normal?

          1 Reply Last reply Reply Quote 0
          • M
            Matts
            last edited by

            @Perry:

            Intel and 3com should in general have better written drivers for Freebsd, by that means lower cpu usages. So it could be worth a test imo.

            Is the same for their Desktop Version ?

            I normally use always Intel because it's default supported by most distro's.

            But are there advantages comparing to the server versions ?

            1 Reply Last reply Reply Quote 0
            • P
              Perry
              last edited by

              t's back up to 35%-40%. When I did a top -S I see that syslogd hovering around 17-18% and the STATE is SELECT.

              Why is syslogd so high is that normal?

              Do you have log on your rules?

              /Perry
              doc.pfsense.org

              1 Reply Last reply Reply Quote 0
              • E
                eyepodder
                last edited by

                No logs on the rules.

                1 Reply Last reply Reply Quote 0
                • E
                  eyepodder
                  last edited by

                  Figure it out. Went back into the system log settings and noticed that I had turned on

                  Log packets blocked by the default rule
                  Hint: packets that are blocked by the implicit default block rule will not be logged anymore if you uncheck this option. Per-rule logging options are not affected.

                  As soon as I deslected it syslogd dropped to barely a reading..

                  1 Reply Last reply Reply Quote 0
                  • M
                    Matts
                    last edited by

                    @eyepodder:

                    Figure it out. Went back into the system log settings and noticed that I had turned on

                    Log packets blocked by the default rule
                    Hint: packets that are blocked by the implicit default block rule will not be logged anymore if you uncheck this option. Per-rule logging options are not affected.

                    As soon as I deslected it syslogd dropped to barely a reading..

                    I also have that on, so that's already an issue. OK :)

                    1 Reply Last reply Reply Quote 0
                    • P
                      Perry
                      last edited by

                      Figure it out. Went back into the system log settings and noticed that I had turned on

                      It's on by default and without using cpu

                      What i would do is as following. (with a default install)

                      Replacing ram, cpu,  motherboard if you got any spare stuff in the lap.
                      try a different freebsd version using pfsense 1.01 and m0n0wall.
                      last resort use another pc.

                      /Perry
                      doc.pfsense.org

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        Yeah logging packets blocked by the default rule certainly shouldn't use ~20% CPU unless you're getting hammered by something that's getting blocked.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.