Issue: Installed 3.03 from 3.02 and CPU is going crazy again

Is there a particular feature that your wiki uses very frequently, that other wikis might not use so much?

Do you have any widgets that display online-locations information on forum-home or another index page?

I have a feeling this is the AJAX link pop-ups. I notice that when I hover over about 10 links on a page that trigger pop-ups, this causes a small spike in CPU. It's likely that if many users are doing this at once, this can cause a more significant CPU spike.

In AdminCP > Settings > Options > VaultWiki: General Settings, set "Enable AJAX Previews of Wiki Articles" to "No". If you notice a significant drop in CPU, the method for generating the pop-ups will have to be revisited: http://www.vaultwiki.org/issues/1955/

I have also seen spikes in CPU for wikis that over-use wiki templates (like several hundred in one article). I would consider the average template usage to be < 10 per article, so if you fall above 10 per article, you may notice an increase in CPU. We have tried to improve the performance of certain templates here: http://www.vaultwiki.org/issues/1952/

Currently my Wiki is in it's very infancy, so there's not a lot of usage/articles there yet, so suggestion #2 wouldn't apply. I'll check into #1 though. Although lately things have seemed better.

Is there anything that would cause CPU spikes after turning the Wiki on, that would then settle down? Caching types of things or something?

Yes, caching of certain items would begin immediately after turning the wiki on, but other types of caching would require visitors.

You might get an influx of visitors that suddenly realize the wiki is back on so they can read that article they wanted to read last week - that also requires a little time to settle down, once everyone feels like they are up-to-date again.

Scheduled tasks would not have occurred since you disabled the wiki. Enabling the wiki would cause the scheduled tasks to play catch-up.

I have found that rebuilding forum styles, plugins, settings, or any cached items like that cause a spike in CPU. This typically happens (sometimes multiple times) when enabling / upgrading the wiki. It would also happen during what may seem like small tweaks to your templates or settings. If you are storing stylesheets (or any other cache) in the file system, updating a large number of files like this at once causes a CPU spike too. If you are using mods like vBOptimise or vBSupercharged, then you have more caches that all need to be updated.

Ok, after your last message I think I can attribute the most recent issues to the caching and updating, scheduled tasks, etc. Right now things seem to be running pretty good and you can probably close this thread as a non-bug at this point.

Thank you for all of your time on the issue!