XenForo + caching = AMAZING

I'm doing tests with Varnish and the results are promising, I believe it is an excellent option integrates it to XF

before:
[root@dev ~]# siege -c 100 -d 1 -t 10s urls.txt
** SIEGE 2.72
** Preparing 100 concurrent users for battle.
The server is now under siege...
Lifting the server siege.. done.

Transactions: 146 hits
Availability: 100.00 %
Elapsed time: 9.89 secs
Data transferred: 0.38 MB
Response time: 4.04 secs
Transaction rate: 14.76 trans/sec
Throughput: 0.04 MB/sec
Concurrency: 59.63
Successful transactions: 220
Failed transactions: 0
Longest transaction: 7.12
Shortest transaction: 0.56

FILE: /usr/local/var/siege.log
You can disable this annoying message by editing
the .siegerc file in your home directory; change
the directive 'show-logfile' to false.

after:
[root@dev ~]# siege -c 100 -d 1 -t 10s urls.txt
** SIEGE 2.72
** Preparing 100 concurrent users for battle.
The server is now under siege...
Lifting the server siege... done.

Transactions: 1906 hits
Availability: 100.00 %
Elapsed time: 9.83 secs
Data transferred: 4.96 MB
Response time: 0.01 secs
Transaction rate: 193.90 trans/sec
Throughput: 0.50 MB/sec
Concurrency: 1.23
Successful transactions: 1954
Failed transactions: 0
Longest transaction: 0.10
Shortest transaction: 0.00

FILE: /usr/local/var/siege.log
You can disable this annoying message by editing
the .siegerc file in your home directory; change
the directive 'show-logfile' to false.
 
I'm confused. I've nginx + memcached (+json +igbinary support). Let's say I use Libmemcached or memcached as backend in XF config file, how it works/What it does exactly ?
I've read some tutorial where in nginx you can do for example :

set $memcached_key "$uri&$args";
memcached_pass memcached;

But that the caching should be done in the PHP.

Not sure to understand. Are both way do different things ? Or memcached_pass is required if I use Libmemcached or memcached as backend in XF ?
I would appreciate if someone could enlighten me.
 
Anybody good at this stuff? Would you be willing to help setup mine to perform better yet?
 
I've upgraded to PHP 5.4.11 (dotdeb repository) but APC (3.1.14) is now causing Apache seg faults. Anyone come up against this, and what was the fix?

Cheers,
Shaun :D
 
PHP 5.3.3 - or whichever stable one comes with Debian squeeze :)

I've recompiled APC, libmemcached and Memcached for PHP 5.4 and tried APC 3.1.13 and 3.1.14 but both cause set faults. Turn off APC and it stops.

No problems with Memcached and libmemcached so just need to fix APC or find an alternative?

Cheers,
Shaun :D
 
That was going to be my next question about recompiling them for 5.4

did you run a make clean before doing the ./configure ?

I'm just looking over my notes from when I upgraded to 5.4, and that is all I did.
 
Anyone has any note on upgrade APC to 3.1.14 on Ubuntu?
I'm still on 3.1.9 and I have to recompile from source if I want the latest.
 
Anyone has any note on upgrade APC to 3.1.14 on Ubuntu?
I'm still on 3.1.9 and I have to recompile from source if I want the latest.
I'd have thought it would be the same as on Debian, so Shaun may be able to advise? I'm on CentOS
 
Anyone has any note on upgrade APC to 3.1.14 on Ubuntu?
I'm still on 3.1.9 and I have to recompile from source if I want the latest.

This is just from memory, but from the command line is should be:

Code:
# wget http://pecl.php.net/get/APC-3.1.14.tgz
# tar -zxvf APC-3.1.14.tgz
# cd APC-3.1.14
# phpize
# ./configure
# make
# make test
# make install

Then restart Apache.
 
did you run a make clean before doing the ./configure ?

I've just tried that but no difference.

Oddly I'm not seeing any strange behaviour at the browser end - the sites seem to run just as quick and there are no problems using them, but the Apache child processes are obviously crashing so it does need addressing.

I'll have a look tomorrow night - I've got more important stuff to do right now ... <unfolds ironing board> :ROFLMAO:
 
This is just from memory, but from the command line is should be:

Code:
# wget http://pecl.php.net/get/APC-3.1.14.tgz
# tar -zxvf APC-3.1.14.tgz
# cd APC-3.1.14
# phpize
# ./configure
# make
# make test
# make install

Then restart Apache.
Same as on CentOS then :-)
 
This is just from memory, but from the command line is should be:

Code:
# wget http://pecl.php.net/get/APC-3.1.14.tgz
# tar -zxvf APC-3.1.14.tgz
# cd APC-3.1.14
# phpize
# ./configure
# make
# make test
# make install

Then restart Apache.
Will this upgrade the current APC?
 
I think I've fixed it - upgraded to libmemcached 1.0.15 and no more seg faults since last Apache restart (and APC isn't fragmenting anymore either!).

Correction: It wasn't libmemcached - is was an apc.ini setting; apc.stat=0

I changed it to apc.stat=1 and the seg faults stopped (as did the fragmentation!). Change it back to zero and seg faults reappear.

The APC default for this setting is 1 so that's why others weren't experiencing the seg faults like I was. (y)
 
Top Bottom