• Isn’t there a more efficient way of writing the code so it doesn’t make 59 database calls to display a single post while in a multisite installation?

    This is according to Query Monitor. Most of them seem to be just getting a single variable from get_network_option, instead of getting all of the variables at once with a single database call.

    With a large multisite installation, that is a lot of calls.

    https://wordpress.org/plugins/wp-piwik/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author braekling

    (@braekling)

    The option handling is done by WP itself, WP-Piwik does not touch the database. Older versions of WP-Piwik tried to store as many options in one WP option (serialized array), but this lead to several errors.

    Can you give some more details on this queries? 59 queries seem to be definitely too many queries at all. Maybe a method is called twice or something similar. Some details will help me to solve the issue.

    Thread Starter docjohn

    (@docjohn)

    Sure, just run the Query Monitor plugin on any WP installation that is also running WP-Piwik and you’ll see first-hand all of the calls WP-Piwik is making to load a single post.

    Plugin Author braekling

    (@braekling)

    Query Monitor shows on my personal blog 1 query per page executed by WP-Piwik. So again, can you please give some more details on the WP-Piwik-related queries which are executed in your environment?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘59 queries per single post in multisite?’ is closed to new replies.