Announcement

Collapse
No announcement yet.

Vbulletin 4.2.4 site getting hammered on CPU. Looks like MYSql. Advice?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vbulletin 4.2.4 site getting hammered on CPU. Looks like MYSql. Advice?

    My VB site is getting hammered by high CPU utilization, and I was looking for some ideas. Here is what is in my system process manager:
    68.36 5.58 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/server.XXXXXXX.com.err --open-files-limit=10000 --pid-file=/var/lib/mysql/mysqld.pid
    My research hasn't turned up anything useful. Does anyone have experience with this type of an issue?
    Thanks
    Chris

  • #2
    There's a mod over at vbulletin.org that may help there. [DBTech] vB Optimise v2 (vB4).

    Comment


    • #3
      Are you using MyISAM tables still? If so, convert your tables to INNODB. Upgrade your MySQL to 5.7 as well.
      Translations provided by Google.

      Wayne Luke
      The Rabid Badger - a vBulletin Cloud customization and demonstration site.
      vBulletin 5 Documentation - Updated every Friday. Report issues here.
      vBulletin 5 API - Full / Mobile
      I am not currently available for vB Messenger Chats.

      Comment


      • #4
        Without proper analysis, and access to your systems, no one can help you other than just guesswork.
        Baby, I was born this way

        Comment


        • #5
          My tables are MyISAM. server is 5.6.35. I will move forward with your suggestions

          Comment


          • #6
            I found this list of tables to update to InnoDB. Are there any others you recommend?
            • alter table attachment engine=InnoDB;
            • alter table datastore engine=InnoDB;
            • alter table deletionlog engine=InnoDB;
            • alter table forum engine=InnoDB;
            • alter table pm engine=InnoDB;
            • alter table pmreceipt engine=InnoDB;
            • alter table pmtext engine=InnoDB;
            • alter table post engine=InnoDB;
            • alter table postparsed engine=InnoDB;
            • alter table searchcore engine=InnoDB;
            • alter table searchgroup engine=InnoDB;
            • alter table searchlog engine=InnoDB;
            • alter table sigparsed engine=InnoDB;
            • alter table subscribethread engine=InnoDB;
            • alter table thread engine=InnoDB;
            • alter table threadviews engine=InnoDB;
            • alter table user engine=InnoDB;
            • alter table usertextfield engine=InnoDB;
            Thanks
            Chris

            Comment


            • #7
              Since you're using MySQL 5.6.X, you can convert every table to INNODB.
              Translations provided by Google.

              Wayne Luke
              The Rabid Badger - a vBulletin Cloud customization and demonstration site.
              vBulletin 5 Documentation - Updated every Friday. Report issues here.
              vBulletin 5 API - Full / Mobile
              I am not currently available for vB Messenger Chats.

              Comment


              • #8
                I am running into issues. Any guidance? This is only on a couple of large - image based tables.

                Comment


                • #9
                  Do as the error says and increase that log file size or store your customavatars in the filesystem under Avatars -> User Picture Storage Type.
                  Translations provided by Google.

                  Wayne Luke
                  The Rabid Badger - a vBulletin Cloud customization and demonstration site.
                  vBulletin 5 Documentation - Updated every Friday. Report issues here.
                  vBulletin 5 API - Full / Mobile
                  I am not currently available for vB Messenger Chats.

                  Comment

                  Related Topics

                  Collapse

                  Working...
                  X