Server load

  • We are new users of the plugin. We loaded initially on our staging server, but didn’t notice any load issues without traffic. After activating on our live server, the load increases significantly and is sustained even after the index is built. The only hook we are using is the ‘relevanssi_hits_filter’ for sorting. The load appears heavy even in times when traffic is very low and no search activity found in the logs. The load increases as soon as the plugin is activated and subsides when deactivated.

    I took a look at the database and find the wp_relevanssi table with 2.4 million records. I unchecked some taxonomies we had in the index and rebuilt, but that did not change the table size much. Can you help us determine the issue and get the plugin activated? We really like the plugin.

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

    (@msaari)

    2.4 million rows in the wp_relevanssi table isn’t a huge amount, but indicates a somewhat large site. There’s no way to significantly reduce that number without affecting the search, but ensuring no useless data is indexed (especially look at custom field indexing settings, using “All” or “Visible” can lead to garbage data going in the index; also have a good list of stopwords) helps a little.

    Relevanssi itself shouldn’t do much when nobody is searching. Can you find out what exactly causes the load? What is your site doing? If you can figure out what database calls or PHP processes cause the load, it would be much easier to figure out how to stop it.

    Thread Starter wmnf

    (@wmnf)

    Very sorry for the delay, I’ve had to tackle many projects lately. Back to testing this issue, it is most definitely the mysqld process that takes off with CPU usage 100-400% while the plugin is active. Looking at the process list in mysql, I see mostly 8-10 of this type of queries…

    | 4605869 | dbuser | localhost | db | Query | 0 | Sending data | SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = ‘_wp_attached_file’ AND meta_value = ‘https://our.s3.amazonaws.com/wp-content/uploads/2015/04/file.jpg’ | 0.000 |

    I consistently see 8-10 new processes such as this while the plugin is activated. We use a plugin for offsite S3 media storage and produce lots of news stories (posts) with images and audio. Any ideas of how I could adjust?

    Plugin Author Mikko Saari

    (@msaari)

    I can tell that query is not directly from Relevanssi: nowhere in Relevanssi code such queries are made. It’s possible there’s some third-party conflict where something Relevanssi does triggers something in another plugin, which triggers something in Relevanssi and so on. That’s something I’ve seen happen, but it can be hard to figure out where exactly. Perhaps you could try to temporarily deactivate the S3 plugin to see if that’s the problem?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Server load’ is closed to new replies.

Tags