[Plugin: WordPress Navigation List Plugin NAVT] NAVT does a lot of queries

  • To display a small menu on my homepage NAVT needs to make 8(!!!) queries!

    1. SELECT option_value FROM wp_options WHERE option_name = ‘wpnavt_installed’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php(946): get_option()]
    2. SELECT * FROM wp_posts WHERE ID = 15 OR ID = 1 OR ID = 9 OR ID = 3 OR ID = 10
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt_fe.php(205): wpdb->get_results()]
    3. SELECT option_value FROM wp_options WHERE option_name = ‘wpnavt_gconfig’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php(946): get_option()]
    4. SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy = ‘category’ AND t.term_id = ’10’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt_fe.php(1103): get_category()]
    5. SELECT option_value FROM wp_options WHERE option_name = ‘wpnavt_iconfig’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php(946): get_option()]
    6. SELECT * FROM wp_posts WHERE ID = 0 OR ID = 30000 OR ID = 42 OR ID = 3 OR ID = 5 OR ID = 2 OR ID = 7
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt_fe.php(205): wpdb->get_results()]
    7. SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy = ‘category’ AND t.term_id = ’15’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt_fe.php(1103): get_category()]
    8. SELECT option_value FROM wp_options WHERE option_name = ‘wpnavt_version’ LIMIT 1
      [wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php(946): get_option()]

    I’m using this plugin for a very long time, and i’ve always been thinking wtf is with wordpress, why it is so slow and now when i’ve got some free time and made a debug, i was shoked man! NAVt does 8 queries, wheareas whole WordPress CMS does 10 queries!

    WTF?? I can’t understand why the author didn’t do some optimization??
    For example why didn’t you set “autoload” to the options that are stored in database in order to extract them all together by using only one query? If this is caused by some certain resons, could you specify them?

    Sorry for my bad english and no offence to author cause in general the plugin is great ??

Viewing 1 replies (of 1 total)

  • Word Press has changed and when I originally wrote the plugin it was optimized. I haven’t really had a optimized release in some time now and I haven’t had a great deal of time to spend making sure you are getting your monies worth – (oh, sorry – you don’t actually pay anything for the plugin.)

    If you’d like to see the author do some actual optimization then donate to it’s support. It is that simple. I hate dragging donations into this but the (very charming) phrase WTF just doesn’t “motivate” anyone (bad English or not).

    When I get some free time (whatever that is) I will optimize the plugin; however, some of the database calls you cite are just part of the performance incurred by WordPress function calls. Sorry, but generally speaking, this type of post(no matter how you mitigate it at the end of the post) is getting very old.

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: WordPress Navigation List Plugin NAVT] NAVT does a lot of queries’ is closed to new replies.