• Resolved e FM

    (@efinancialmodels)


    The plugin consumed too many resources today and crashed our server.

    I am wondering if the new features added consume more resources than before. We decided to use this plugin assuming it is slick and only queries optimized for performance run with this plugin. If you could recheck the resource consumption of this plugin. We would like this to use as less resources as possible.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Pär Thernström

    (@eskapism)

    Hi @efinancialmodels,

    the plugin still uses very few resources. For example it writes to the database only when an action is performed (post edit, user login, plugin update, etc).

    Any chance you could elaborate what “too many resources” mean? Was it like out of memory errors, did the database get to large, or what did happen? I have not experienced this myself but I am of course interesting in finding any errors or memory or cpu issues in the plugin.

    Thread Starter e FM

    (@efinancialmodels)

    Dear @eskapism, thanks for your reply.

    The database server hangs up if there are too many queries made dot eh database. Your plugin showed up in the log just before our website goes down. Its not a PHP server issue, its a database (Maria DB) server issue. Many database queries get stuck and cannot be processed and then hang-up the server.

    What I noticed is that you added many more features and might have changed some of the queries. We don’t need all this. We are looking for a lightweight pluign that uses the minimum of resources and load on our server. If you could recheck all INSERT and UPDATE queries this plugin does to the database to see if there is anything that could be optimized.

    Plugin Author Pär Thernström

    (@eskapism)

    @efinancialmodels On a regular page view on the front end, Simple History does not use the DB. It only queries the db when viewing the log and it only writes to the db when something has happened (like a post is updated, a user is logging in, and so on).

    There can be compaibility issues with other plugins and code, for example if another plugin every second updates a post, then maybe Simple History also logs that change, causing a lot of db inserts. or if many users are trying to login there can be a lot of inserts.

    Do you have a log of what queries took a long time so the db got stuck? Also, how many rows are stored in the simple history tables (you can see this on the Simple History » Debug page). I love to debug this further to see if there is anything I can do.

    Regarding new features: yes, I am adding more features because I have more time to work on the plugin now. It’s features that have been on the todo list since 2015 🙂 I work hard to make sure they do not affect performance. Like the Admin Bar Quick View that shows the latest event in the admin bar, the events are only loaded when you show the menu, not before.

    Thread Starter e FM

    (@efinancialmodels)

    Dear Paer, @eskapism, thank you for checking this and for watching the resource consumption. Yes, we are aware and constantly checking potential conflicts and optimze. We do appreciate if this plugin can keep performing lean and with the least resource consumption possible. Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Recent Resource Consumption’ is closed to new replies.