Ad Widget

Collapse

Separate database server slows down GUI?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • satchelp
    Junior Member
    • Jul 2008
    • 13

    #1

    Separate database server slows down GUI?

    I recently installed Zabbix 1.4.6 with a separate frontend and MySQL backend. Both servers are running SuSE 10. I noticed this was running slower than I had expected (with zero hosts setup it was taking around 5-6 seconds to switch between any page within the GUI). When I changed the configuration to have the frontend also act as the database server, the interface responds quickly as I would expect.

    Is this a normal performance hit when separating these roles? The my.cnf file is the same between the two servers and they are on the same network segment (I have no other network related problems on any servers on this network). I cannot think what would be causing this additional slowdown.

    Thanks,

    Satchel
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    It does look like a DNS delay caused by incorrect DNS configuration (probably on MySQL server side). Also you may check PHP configuration and enable persistent MySQL connections.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • globifrosch
      Member
      • Sep 2005
      • 74

      #3
      for sure this is the name resolving in mysqld.

      try to add skip-name-resolve under [mysqld] in /etc/mysql/my.cnf (or wherever your global my.cnf is located)

      remember to check your mysql users to not contain dns names in host restrictions.

      or fix the reverse lookup dns for all involved systems.

      Comment

      • satchelp
        Junior Member
        • Jul 2008
        • 13

        #4
        Thanks to Alexei and globifrosch! Changing skip-name-resolve in my.cnf and adding adding mysql.allow_persistent = on in the php config seems to have fixed the issue.

        --Satchel

        Comment

        Working...