Number of Processor Cores

[Gene Steinberg]

On a newly-configured server with two Intel(R) Xeon(R) CPU E5-2620, 6 cores each, I set the counts in XCache 3.1.0 to 12, counting both cores.

But when configured, XCache shows 16 splits.

Also, what are proper TTLs to set for WordPress blogs and XenForo forums?

And even the amount of memory.

With 32GB, I can go as high as needed for maximum performance.

Peace,

Gene

[Xuefer]

On Thursday, July 31, 2014, Gene Steinberg <genest...@gmail.com> wrote:

On a newly-configured server with two Intel(R) Xeon(R) CPU E5-2620, 6 cores each, I set the counts in XCache 3.1.0 to 12, counting both cores.

But when configured, XCache shows 16 splits.

It's round up to 2^n

the balance algorithm (between splits) is simply base on performance not to balance the split cache usage evenly. if some split (e.g. #1) is almost full and others (e.g. #4) almost empty, it the (big) item gonna cache is decided to save into #1 won't be rearrange to be in #4. this leads to out of memory, fail to cache. lowering split count or increase xcache.size, should reduce this symptom

 

Also, what are proper TTLs to set for WordPress blogs and XenForo forums?

And even the amount of memory.

With 32GB, I can go as high as needed for maximum performance.

about xcache.size: check xcache admin page after running for a while, see if the cache is full  

Peace,

Gene

--

---
You received this message because you are subscribed to the Google Groups "XCache" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xcache+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gene Steinberg]

What I see so far is that the cache, set at 256M, isn’t filling. The hits increase for a few minutes, then zero out. Seems everything is properly activated and the host’s support people claim it’s OK. But it’s not.

My settings:

Module Info

XCache

XCache Version	3.1.0
Modules Built	cacher

Directive	Local Value	Master Value
xcache.coredump_directory	no value	no value
xcache.disable_on_crash	Off	Off
xcache.experimental	Off	Off
xcache.test	Off	Off

XCache Cacher

XCache Cacher Module	enabled
Readonly Protection	disabled
Page Request Time	2014-07-31 15:09:27
Cache Init Time	2014-07-31 14:48:11
Cache Instance Id	22205
Opcode Cache	enabled, 268,435,456 bytes, 16 split(s), with 8192 slots each
Variable Cache	enabled, 134,217,728 bytes, 16 split(s), with 8192 slots each
Shared Memory Schemes	mmap

Directive	Local Value	Master Value
xcache.admin.enable_auth	Off	Off
xcache.allocator	bestfit	bestfit
xcache.cacher	On	On
xcache.count	12	12
xcache.gc_interval	0	0
xcache.mmap_path	/dev/zero	/dev/zero
xcache.readonly_protection	Off	Off
xcache.shm_scheme	mmap	mmap
xcache.size	256M	256M
xcache.slots	8K	8K
xcache.stat	On	On
xcache.ttl	3600	3600
xcache.var_allocator	bestfit	bestfit
xcache.var_count	12	12
xcache.var_gc_interval	300	300
xcache.var_maxttl	7200	7200
xcache.var_namespace	no value	no value
xcache.var_namespace_mode	0	0
xcache.var_size	128M	128M
xcache.var_slots	8K	8K
xcache.var_ttl	3600	3600

You received this message because you are subscribed to a topic in the Google Groups "XCache" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/xcache/mKtp81e1KyQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to xcache+un...@googlegroups.com.