Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Devtard

    (@devtard)

    Hello, the more operations the plugin does, the more resource-intensive it is. You may be experiencing this issue if your posts are long, you have many keywords and word separators set up etc.

    Unfortunately, there’s not much that can be done about this – unless you are okay with limiting the plugin’s functionality, e.g. by letting it analyze only a certain number of characters, deleting unused word separators etc.

    Thread Starter burlyqlady

    (@burlyqlady)

    I can’t do any of that at the moment. I would happily pay for something that doesn’t crash my site when I try to use it?

    can you give me more examples of what I can do? currently I can’t run the plugin at all anymore.

    Plugin Author Devtard

    (@devtard)

    You can try the following:
    -Limit the number of posts processed per batch. Try setting just one and increasing the time delay. This will slow down the bulk tagging process, but also decrease the server load.
    -Delete unused word separators. Even better: Let the plugin replace all non-alphanumeric characters with spaces and use only the space as a word separator.
    -Let the plugin analyze only a certain part of posts, say only the first 1000 characters.
    -Deactivate the tag stripping and HTML entities decoding features.

    What happens when your site crashes? Are you seeing any errors etc? How many keyword sets and taxonomies do you have?

    Thread Starter burlyqlady

    (@burlyqlady)

    Thank you so much for your fast reply!!

    I get a 500 error but mostly a 503 error, yes.
    I have a total of 288 sets of keywords.
    I’ve got 327 tags.

    Plugin Author Devtard

    (@devtard)

    Lots of related keywords and multiple taxonomies defined in the group editor can also cause the plugin to be resource-hungry.

    Although the plugin hasn’t really been created with efficiency in mind (there’s e.g. the multiple taxonomies-related issue I know about), my experience is that the plugin does its job fine with default settings even in shared web hosting environments (unless the plugin’s database contains thousands of keywords, of course).

    If my suggestions don’t help, maybe consider moving the website to a better server?

    Thread Starter burlyqlady

    (@burlyqlady)

    Yes, I’m looking into doing that now. I’m actually using a Managed DirectAdmin VPS with 100 GB Disk Space 10 TB’s / Gig Port 1 GB RAM + 2 vCPU Core
    I’m paying $40 plus an add-on of $20 in VPS Additonal RAM of 2 GB, yet CPU keeps maxing out, especially when running this plugin.

    Plugin Author Devtard

    (@devtard)

    Hmm, interesting. In case you’ll still be experiencing the aforementioned issues, I’d definitely try to talk to someone from your web host’s support team who might be able to give you a better informed opinion regarding the situation.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Maxing out server resources’ is closed to new replies.