The code is essentially same for the free and the Premium, so I’m afraid the problem will remain. Relevanssi can be quite CPU intensive. How large is your database?
Hi Mikko!
The database is about 100 MB.
When I deactivated the plugin the CPU usage was normal again – but unfortunately just for couple of hours. We just discovered that we issued massive CPU load this night even though the plugin was deactivated *gah* – so I´m not sure if Relevanssi is the main problem anymore.
We have had these problems for just two weeks now.
Can tell that we are using a lot of plugins on this site, about 40.
None of them is a cache plugin.
The behaviour comes now and then.
This may not be the right place to put this, but I´d appreciate if anyone have any idea what can be causing this.
I’m more interested in number of posts than size in megabytes; Relevanssi gets a bit too heavy when you reach about tens of thousands of posts, I think.
We have maximum 2000 posts so far in the db.
But finally we found what was causing the massive CPU load (which just happened now and then) – it was because of a temp folder that for weeks had saved hundreds of thousands session files which shouldn´t be saved there. Those should normally be deleted automatically.
Thus, it wasn´t because of the Relevanssi plugin – this time. But I still think this plugin is or can cause some performance issues.
Because we deleted the plugin and wasn´t running it for 2 weeks and everything worked good on the server. 2 days ago we installed the plugin again this time Premium version and we started to issue performance problems again. It is not the same problem as before as we wan see. But again I´m not sure if its this plugin causing it this time, but it might be it. We can´t see anything in any logs.
Gah it is frustrating. Can tell that WP-site is on a Windows server.
If anyone have any clue I´d appreciate if you shared that information.
Sorry, I’m rather clueless about server performance issues. I’ll gladly fix Relevanssi to be more efficient, but unfortunately I don’t know how.