Constraining for performance

  • Resolved gsf747

    (@gsf747)


    8 years, 9 months ago

    We have a WP site running on AWS with a smallish database server but it runs fine because little of it is dynamic (no comments, etc.) and we’re caching wherever possible. We love this plugin but our caching fails and the database grinds to a halt as soon as we enable it due to misbehaving bots bouncing around the dynamic calendar URLs.

    Can we drop features or otherwise constrain the plugin to lessen the number and complexity of database calls? We’re happy to mask URL paths as long as views of a basic calendar and individual events are still available. Alternatively, are there DB tweaks (indexes or views) we can put in place to improve performance?

    https://wordpress.org/plugins/all-in-one-event-calendar/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Benjamin

    (@bsokic)

    8 years, 9 months ago

    Hi,

    Which version are you using?

    Thread Starter gsf747

    (@gsf747)

    8 years, 9 months ago

    Hi! We’re using version 2.2.1.

    jeffrey wilcox

    (@jeffrey-wilcox)

    8 years, 9 months ago

    I might be way off base, but can’t you add to robots.txt?

    Thread Starter gsf747

    (@gsf747)

    8 years, 9 months ago

    Yes, the pages are disallowed in the robots.txt, which is why I labeled these bots “misbehaving.” The bots weren’t really the problem, however, as their activity wasn’t that intense (a hit every few seconds). The problem was that even the moderate traffic we saw on the calendar pages really taxed our database and PHP processes.

    Benjamin

    (@bsokic)

    8 years, 9 months ago

    I think the only way to solve this problem is to upgrade the host, server.. We unfortunately can not do anything more from our side.

    Thread Starter gsf747

    (@gsf747)

    8 years, 9 months ago

    Understood. The plugin presents a dynamic interface (one of the reasons we like it) and that necessarily increases load on the backend. Thanks for considering the issue.

    Benjamin

    (@bsokic)

    8 years, 9 months ago

    No problem.

    Take care,
    Ben

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Constraining for performance’ is closed to new replies.