Oh, this is BuddyPress 1.6.2 on WP 3.5 in Multisite mode.
And I just noticed this is coming from APC Opcode Cache which is suddenly massively running out of space with a HUGE cache full count. I’m afraid BuddyPress IS a bit big for this low-end VPS 🙁
If you’re using multisite and any other large or memory-hungry plugins, then yes. Maybe adjust your APC settings to use less memory; what will be stored may be released as it runs past its memory allocation, but it would prevent the warnings.
@Paul is there any general rule of thumb for minimum server configuration size?
@all here is some info about my experience for others that would like to know more about size issues in advance:
I’m using the smallest VPS on http://www.kimsufi.com/fr/vks/index.xml (512MB) with 64bit Debian. With hindsight I should probably have chosen a 32bit install because that is said to consume less memory but still it is enough for one WordPress Multi-site and some of the bigger plugins like Jetpack with not too many sites and average traffic on the network. Installed Nginx/PHP5-FPM instead of Apache and for caching I added APC and WP Super Cache (in PHP mode) which did help a lot in getting the max out of the little machine. Pretty high speeds I must say, but loading BuddyPress on top of that and the thing started squeaking.
I have removed BuddyPress and cleared the completely fragmented opcode cache (had to restart PHP service because it refused to be cleared through the manager) and all is well again.
Maybe it would be possible to run a single site WP installation with BuddyPress on such a small server… or even multi-site but without any other memory-hungry plugins… or maybe some more tweaking of the APC settings (cache size and ttl) might make it pass… but I’m not going to try that on a live install 😉
Server config is not my area of expertise, so I can’t advise.