This is actually fairly easy, it presents the full contents of the INFO to the xenforo admin template. Add {xen:helper dump, $redis} into the admin template SV_Redis_info to see the full information.it would be great, to see on ACP Widget for Redis also the Redis memory usage peak. Thats the only thing I miss.
This is a matter of server configurationOk, and a documentation I understand for a master/slave config on same maschine...
IIRC @Xon's addon can't specify the redis db number but wordpress can, so switch it around, Xenforo Redis use db #0 and WP use Redis db #1I have a Wordpress blog using Redis, how can I make my XF forum use a separate Redis cache?
There are 16 databases by default, Wordpress is using 0.
I have a Wordpress blog using Redis, how can I make my XF forum use a separate Redis cache?
There are 16 databases by default, Wordpress is using 0.
It can. example with all options, not well documented tho.IIRC @Xon's addon can't specify the redis db number but wordpress can, so switch it around, Xenforo Redis use db #0 and WP use Redis db #1
$config['cache']['backendOptions']['database'] = 1;
- Option "slave-select" can now be a closure or a string. Default is "preferLocalSlave".
- String options:
- preferLocalSlave - fetches IP's via a shell exec
- preferLocalSlaveLocalDisk - fetches IP's via a shell exec, but caches to /tmp/local_ips
- preferLocalSlaveAPCu - fetches IP's via a shell exec, but caches to APCu
- NOT RECOMMENDED
- New option 'sentinel_persistent' (true/false, uses 'persistent' option if...
This is a bit tricky as some of my add-ons can use different Redis instances, and it is a very heavyweight operation to-do. I'm planning on revising how this add-on presents redis instances to other add-ons before XF2, so I'll look into itIt would be really useful to flushall from admincp.
screen
iostat -c -t 30 > /tmp/cpu_stats.log
cat /tmp/cpu_stats.txt | grep -v iowait | awk '{print $5;}' | sort -rn | more
This update synchronizes with the Credis and Cm_Cache_Backend_Redis library's upstream, which results in several breaking changes in configuration.
This is a breaking change if you use sentinel support
The following configuration keys have been renamed:
- sentinel_master_set renamed to sentinel_master
- slave-select renamed to slave_select_callable
- sentinel_persistent renamed to...
'server' => '127.0.0.1:26379'
'server' => 'tcp://127.0.0.1:26379'
'server' => '127.0.0.1', 'port' => 26379,
- Update backend redis connector library.
- Bugfix pure php connector, only impacts custom add-ons directly calling the redis library.
- load_from_slaves option can now be 2 to include the master in the list of read-only instances to connect to.
It is just the XML being out of date, the files are correct. I've re-uploaded the correct .zip packageAfter install/upgrade, it's still showing as v1.4.0 ?!
Q. CPU Steal is mentioned as causing latency issue, how do I check this.
A. On Linux, run:
Code:screen iostat -c -t 30 > /tmp/cpu_stats.log
Then after a day or so; check your max CPU steal:
Code:cat /tmp/cpu_stats.txt | grep -v iowait | awk '{print $5;}' | sort -rn | more
2.02
1.84
1.82
1.71
1.67
1.61
1.53
1.52
1.50
1.48
1.43
1.42
1.41
1.35
1.33
1.30
1.30
1.29
1.29
1.28
1.27
1.27
1.26
1.26
1.25
1.24
We use essential cookies to make this site work, and optional cookies to enhance your experience.