Bug Xcache brings up Opcache is not working

[D19RNY]

vB Optimise: Test Setup
Running Test: Connection to xcache
Test completed successfully
Running Test: Store Cache
Test completed successfully
Running Test: Fetch Cache
Your Opcache Operator extension is functioning, however it is unable to store data. Please check your extension configuration.
Running Test: Flush Cache
Test completed successfully

This problem is intermittent, it works sometimes sometime it brings that error.


[xcache]
xcache.shm_scheme = "mmap"
xcache.size = 90M
xcache.count = 2
xcache.slots = 5K
xcache.ttl = 3600
xcache.gc_interval = 900
xcache.var_size = 8M
xcache.var_count = 2
xcache.var_slots = 5K
xcache.var_ttl = 3600
xcache.var_maxttl = 7200
xcache.var_gc_interval = 900
xcache.test = Off
xcache.readonly_protection = Off
xcache.mmap_path = "/dev/zero"
xcache.coredump_directory = ""
xcache.cacher = On
xcache.stat = On
xcache.optimizer = Off
[xcache.coverager]
xcache.coverager = Off
xcache.coveragedump_directory = ""

 

[Fillip H.]

XCache is notorious for not wanting to function on a bunch of server configurations. Would it be possible for you to switch to using Memcached instead? It's a whole lot easier to setup, and thus far I've not ran into a single instance where it didn't work

 

[D19RNY]

XCache is notorious for not wanting to function on a bunch of server configurations. Would it be possible for you to switch to using Memcached instead? It's a whole lot easier to setup, and thus far I've not ran into a single instance where it didn't work

We were running memcached, but we keep getting server load spikes, and they are happening right this minute. 100 users online with spikes up to 8.00 :/ So i tried xcache to see if it causes the same issue.

 

[Fillip H.]

I see. I can't say I know of any reason why it would cause those issues, but what I do know is that that error means that XCache doesn't retain its cache data.

It's unfortunately something that's beyond my skill to help diagnose - I spent several weeks trying to get XCache working for DBTech back ~6 months ago, but neither me nor Deceptor were able to figure it out. That's why we ended up going Memcached and why I recommend it to everybody I know

 

[D19RNY]

I see. I can't say I know of any reason why it would cause those issues, but what I do know is that that error means that XCache doesn't retain its cache data.

It's unfortunately something that's beyond my skill to help diagnose - I spent several weeks trying to get XCache working for DBTech back ~6 months ago, but neither me nor Deceptor were able to figure it out. That's why we ended up going Memcached and why I recommend it to everybody I know

OK, i will put memcached back on, what would be the best settings for my server?

http://fivestargamerz.com/sysinfo/index.php?disp=dynamic

Thanks


/usr/local/bin/memcached -u nobody -d -m 128 -l 127.0.0.1 -p 11211


That is what i used

 

[Fillip H.]

If you have 2.5 GB RAM you might want to consider giving Memcached a little bit more than 128.

Considering you're sitting at 51% usage at the time of writing this, I'd suggest trying 1024 - if that ends up slowing down your server / getting out of memory errors, you can try lowering it to 512. It should be fine, though.

Generally, the more RAM you can spare to the cacher, the less time it has to spend deleting old cache data (for users who may have gone AFK or somesuch) to make room for new cache data.

That being said, going completely overboard would leave your Apache / MySQL starved, so it's basically trial and error what works for you when your server is under stress from peak hours