Archive for September, 2011

Three Free PHP Accelerator:APC、eAccelerator、XCache Comparison

I have been looking for articles on PHP acceleration,Chance to seeKill offThis article,Feeling good,For everyone to share,Again thank kill off。

one、PHP Accelerator Introduction

PHP is an accelerator in order to improve the efficiency of PHP,Thus from PHP opcode cache,PHP execution behind this would not resolve the converted,PHP opcode can invoke direct,On such speed is increased a lot。

Apache's request to use mod_php、In response to the flow of execution:

1、Apache receives a request。
2、Apache pass the request to the mod_php。
3、mod_php locate a disk file,And loaded into memory。
4、mod_php compile the source code tree becomes opcode。
5、mod_php execution opcode tree。

PHP is the fourth step of the corresponding accelerator,Its purpose is to prevent repeated every request to compile PHP PHP code,Because in high-traffic sites,Often not a lot of compiler execution speed fast? So there are a bottleneck that compiles PHP affects both the speed and load server load,In order to solve this problem,PHP accelerator was born。

two、PHP Accelerator Installation and Configuration

1、APC Installation and Configuration

APC stands for Alternative PHP Cache,The official translation is called "Optional PHP cache",It is an extension of PHP PECL,It seems to be using facebook,Here begin the installation (ubuntu environment):
$wget http://pecl.php.net/get/APC-3.0.19.tgz
$tar xvzf APC-3.0.19.tgz
$cd APC-3.0.19/APC-3.0.19
$/usr/local/php/bin/phpize
$./configure –enable-apc –enable-apc-mmap –with-php-config=/usr/local/php/bin/php-config
$make
$sudo make install

Here we configure APC,Because I changed the path of PECL extension,So I have to move under the compiled file:
$sudo mv /usr/local/php/lib/php/extensions/no-debug-non-zts-20060613/apc.so /usr/local/php/lib/php/extensions/PECL

Then we edit the php.ini configuration file,Please add the following code to the php.ini to:
extension_dir = “/usr/local/php/lib/php/extensions/PECL”
extension = apc.so
; APC
apc.enabled = 1
apc.shm_segments = 1
apc.shm_size = 64
apc.optimization = 1
apc.num_files_hint = 0
apc.ttl = 0
apc.gc_ttl = 3600
apc.cache_by_default = on

This will restart apache in phpinfo()Information display。

2、Installation configuration eAccelerator

eAccelerator is actually the predecessor of truck-mmcache,Because the development truk-mmcache Zend people were given amnesty,Therefore, the development eAccelerator who inherited some of the characteristics truk-mmcache,EAccelerator accelerator design。Installation is as follows:
$wget http://jaist.dl.sourceforge.net/sourceforge/eaccelerator/eaccelerator-0.9.5.tar.bz2
$tar -jxf eaccelerator-0.9.5.tar.bz2
$cd eaccelerator-0.9.5
$/usr/local/php/bin/phpize
$./configure –enable-eaccelerator=shared –with-php-config=/usr/local/php/bin/php-config
$make
$sudo make install
$sudo mv /usr/local/php/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so /usr/local/php/lib/php/extensions/PECL

The following code to your php.ini file
extension = eaccelerator.so
; eAccelerator
eaccelerator.shm_size = “16”
eaccelerator.cache_dir = “/tmp/eaccelerator”
eaccelerator.enable = “1”
eaccelerator.optimizer = “1”
eaccelerator.check_mtime = “1”
eaccelerator.debug = “0”
eaccelerator.filter = “”
eaccelerator.shm_max = “0”
eaccelerator.shm_ttl = “0”
eaccelerator.prune_period = “0”
eaccelerator.shm_only = “0”
eaccelerator.compress = “1”
eaccelerator.compress_level = “9”

Create cache directory,Restart apache

$sudo mkdir /tmp/eaccelerator
$sudo chmod 777 /tmp/eaccelerator
$sudo /usr/local/apache/apachectl restart

At phpinfo()Check whether the installation was successful.

3、Installation and Configuration XCache

XCache own people as something to be developed,I also do little rookie proud,And XCache in terms of speed and performance are doing well。Here quickly let us taste it now!

$wget http://xcache.lighttpd.net/pub/Releases/1.2.2/xcache-1.2.2.tar.gz
$tar xvzf xcache-1.2.2.tar.gz
$cd xcache-1.2.2
$/usr/local/php/bin/phpize
$./configure –enable-xcache –enable-xcache-coverager –with-php-config=/usr/local/php/php-config
$make
$sudo make install
$sudo mv /usr/local/php/lib/php/extensions/no-debug-non-zts-20060613/xcache.so /usr/local/php/lib/php/extensions/PECL

In php.ini add configuration information:

extension = xcache.so
; xcache
xcache.admin.user = “admin”
xcache.admin.pass = “(carried out) echo ’(Your password)’|md5sum(Resulting ciphertext)”
;
xcache.size = 24M
xcache.shm_scheme = “mmap”
xcache.count = 2
xcache.slots = 8k
xcache.ttl = 0
xcache.gc_interval = 0

xcache.var_size = 8M
xcache.var_count = 1
xcache.var_slots = 8k
xcache.var_ttl = 0
xcache.var_maxttl = 0
xcache.var_gc_interval = 300
xcache.test = Off
xcache.readonly_protection = On
xcache.mmap_path = “/tmp/xcache”
xcache.coredump_directory = “”
xcache.cacher = On
xcache.stat = On
xcache.optimizer = Off
;
xcache.coverager = On
xcache.coveragedump_directory = “”

Create cache directory,Restart apache

$sudo mkdir /tmp/xcache
$sudo chmod 777 /tmp/xcache
$sudo /usr/local/apache/bin/apachectl restart

To view the phpinfo()Information now!

three、PHP Accelerator Test

1、test environment

hardware: AMD Athlon 64 X2 Dual Core Processor 4400+ @ 2.2GHz CPU, 2GB memory. 160GB SATA hard drive

software: Linux Ubuntu server Gutsy 7.10, Apache 2.2.4, MySQL 5.0.45 And PHP 5.2.3

Test instructions: ab -c5 -n3000 http://example.com/ (We are using Apache Benchmark (from) tool,5 concurrent connections,3000Request times)

2、Test Results

No accelerator:

Document Path: /
Document Length: 21757 bytes
Concurrency Level: 5
Time taken for tests: 288.255212 seconds
Complete requests: 3000
Failed requests: 0
Write errors: 0
Total transferred: 66777000 bytes
HTML transferred: 65271000 bytes
Requests per second: 10.41 [#/sec] (mean)
Time per request: 480.425 [ms] (mean)
Time per request: 96.085 [ms] (mean, across all concurrent requests)
Transfer rate: 226.23 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.5 0 19
Processing: 181 479 186.0 444 1822
Waiting: 166 461 184.7 427 1708
Total: 181 479 186.0 444 1822
Percentage of the requests served within a certain time (ms)
50% 444
66% 525
75% 577
80% 619
90% 732
95% 819
98% 946
99% 1012
100% 1822 (longest request)

APC 加速器:

Document Path: /
Document Length: 21757 bytes
Concurrency Level: 5
Time taken for tests: 98.530068 seconds
Complete requests: 3000
Failed requests: 0
Write errors: 0
Total transferred: 66777000 bytes
HTML transferred: 65271000 bytes
Requests per second: 30.45 [#/sec] (mean)
Time per request: 164.217 [ms] (mean)
Time per request: 32.843 [ms] (mean, across all concurrent requests)
Transfer rate: 661.84 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 2
Processing: 58 163 71.2 155 2452
Waiting: 53 158 69.6 150 2329
Total: 58 163 71.2 155 2452
Percentage of the requests served within a certain time (ms)
50% 155
66% 178
75% 193
80% 204
90% 235
95% 258
98% 285
99% 302
100% 2452 (longest request)

eAccelerator加速器:

Document Path: /
Document Length: 21757 bytes
Concurrency Level: 5
Time taken for tests: 95.983986 seconds
Complete requests: 3000
Failed requests: 0
Write errors: 0
Total transferred: 66777000 bytes
HTML transferred: 65271000 bytes
Requests per second: 31.26 [#/sec] (mean)
Time per request: 159.973 [ms] (mean)
Time per request: 31.995 [ms] (mean, across all concurrent requests)
Transfer rate: 679.39 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 3
Processing: 57 159 91.3 148 3830
Waiting: 50 152 89.8 142 3704
Total: 57 159 91.3 148 3830
Percentage of the requests served within a certain time (ms)
50% 148
66% 174
75% 193
80% 205
90% 239
95% 263
98% 289
99% 309
100% 3830 (longest request)

XCache加速器:

Document Path: /
Document Length: 21757 bytes
Concurrency Level: 5
Time taken for tests: 99.76300 seconds
Complete requests: 3000
Failed requests: 0
Write errors: 0
Total transferred: 66777000 bytes
HTML transferred: 65271000 bytes
Requests per second: 30.28 [#/sec] (mean)
Time per request: 165.127 [ms] (mean)
Time per request: 33.025 [ms] (mean, across all concurrent requests)
Transfer rate: 658.19 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 2
Processing: 59 164 83.4 155 3367
Waiting: 52 156 66.4 148 1802
Total: 59 164 83.4 155 3367
Percentage of the requests served within a certain time (ms)
50% 155
66% 178
75% 196
80% 206
90% 237
95% 263
98% 287
99% 305
100% 3367 (longest request)

3、Results Summary

Request Time(second)Single request time(millisecond)The maximum memory footprint(MB)The minimum memory footprint(MB)
None10.4196.082424
APC30.4532.842121
eAccelerator31.2631.992318
XCache30.2833.022919

four、PHP accelerator comparison summary

1、EAccelerator obtained by testing at request time and overall memory footprint area is best。

2、Test results using the ratio of the accelerator by accelerator-free request time about three times faster。

3、By observing the various official,XCache is the fastest updates,It also shows that most of the development。

These are the summary results,You might ask me in the end with the accelerator good? I can only tell you,First of all,Use must be better than no,Secondly, each of the accelerator some parameters can tune,So according to your system environment,then,Personally, I think you can study in detail under eAccelerator and XCache,Both still great potential,Finally, I get a map from the results of a more professional test site:

cache

Comments

How to view real-time under linux mysql current number of connections? ? Command is what?

mysqadmin -uroot -p processlist
Details can be seen in connection.

If you just want to see the number of connections.
Direct hit mysqladmin status
Threads is the number of connections

Comments

Server security plan

To ensure that my CentOS machines run as efficiently and securely as possible, I disable a number of services after each installation. The end result is a system that accepts ssh connections on TCP port 22, and on one or more service ports that are in use by the applications hosted on the platform. To get to this state, I go through and disable numerous services that come enabled by default. Here is the default list of services that are enabled after a CentOS 4.4 installation:

$ chkconfig –list | grep on

etc             0:off   1:off   2:off   3:on    4:on    5:on    6:off
messagebus      0:off   1:off   2:off   3:on    4:on    5:on    6:off
smartd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
portmap         0:off   1:off   2:off   3:on    4:on    5:on    6:off
sendmail        0:off   1:off   2:on    3:on    4:on    5:on    6:off
netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off
cups            0:off   1:off   2:on    3:on    4:on    5:on    6:off
irqbalance      0:off   1:off   2:off   3:on    4:on    5:on    6:off
rpcgssd         0:off   1:off   2:off   3:on    4:on    5:on    6:off
xfs             0:off   1:off   2:on    3:on    4:on    5:on    6:off
isdn            0:off   1:off   2:on    3:on    4:on    5:on    6:off
autofs          0:off   1:off   2:off   3:on    4:on    5:on    6:off
gpm             0:off   1:off   2:on    3:on    4:on    5:on    6:off
apmd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
crond           0:off   1:off   2:on    3:on    4:on    5:on    6:off
acpid           0:off   1:off   2:off   3:on    4:on    5:on    6:off
microcode_ctl   0:off   1:off   2:on    3:on    4:on    5:on    6:off
pcmcia          0:off   1:off   2:on    3:on    4:on    5:on    6:off
cpuspeed        0:off   1:on    2:on    3:on    4:on    5:on    6:off
xinetd          0:off   1:off   2:off   3:on    4:on    5:on    6:off
rpcidmapd       0:off   1:off   2:off   3:on    4:on    5:on    6:off
readahead_early 0:off   1:off   2:off   3:off   4:off   5:on    6:off
readahead       0:off   1:off   2:off   3:off   4:off   5:on    6:off
sshd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
anacron         0:off   1:off   2:on    3:on    4:on    5:on    6:off
network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
kudzu           0:off   1:off   2:off   3:on    4:on    5:on    6:off
syslog          0:off   1:off   2:on    3:on    4:on    5:on    6:off
nfslock         0:off   1:off   2:off   3:on    4:on    5:on    6:off
rawdevices      0:off   1:off   2:off   3:on    4:on    5:on    6:off
mdmonitor       0:off   1:off   2:on    3:on    4:on    5:on    6:off
haldaemon       0:off   1:off   2:off   3:on    4:on    5:on    6:off

Several of these services are required, but several others serve no purpose in my environment, and use CPU and memory resources that would be better allocated to my applications. Since I don’t use RPC services, autofs or NFS, those are the first to get disabled:

$ /sbin/chkconfig –level 0123456 portmap off
$ /sbin/chkconfig –level 0123456 nfslock off
$ /sbin/chkconfig –level 0123456 netfs off
$ /sbin/chkconfig –level 0123456 rpcgssd off
$ /sbin/chkconfig –level 0123456 rpcidmapd off
$ /sbin/chkconfig –level 0123456 autofs off

I also don’t allow individual hosts to receive mail from the outside world, so sendmail gets nixed next:

$ /sbin/chkconfig –level 0123456 sendmail off

On server platforms, who needs printing?:

$ /sbin/chkconfig –level 0123456 cups off

Now we get to the font server, isdn capabilities, console mouse and pcmcia support. I don’t use these services on my servers, so they get disabled as well:

$ /sbin/chkconfig –level 0123456 xfs off
$ /sbin/chkconfig –level 0123456 isdn off
$ /sbin/chkconfig –level 0123456 gpm off
$ /sbin/chkconfig –level 0123456 pcmcia off

Once these services are disabled (and optionally stopped with the service command or a reboot), my netstat output looks nice and clean:

$ netstat –tcp –udp –listening

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 *:ssh                       *:*                         LISTEN

This has served me well over the years, since it reduces boot time (less rc scripts to run), and frees up additional resources for my applications (while this isn’t substantial, every page of memory helps!).

Comments

CentOS 5 The OpenSSL and OpenSSH upgrade

CentOS 5 The OpenSSL and OpenSSH upgrade

2010-10-24 23:44

The OpenSSL and OpenSSH upgraded。CentOS 5.2 is brought OpenSSL 0.9.8b,OpenSSH is 4.0p1。Upgrade follows:

 

openssh latest version (http://www.openssh.com/portable.html)

 

wget http://www.openssl.org/source/openssl-0.9.8j.tar.gz

 

tar zxvf openssl-0.9.8j.tar.gz

 

cd openssl-0.9.8j

 

./config –prefix=/usr

 

make

 

make test

 

make install

 

wget http://openbsd.noc.jgm.gov.ar/pub/OpenBSD/OpenSSH/portable/openssh-5.2p1.tar.gz

 

tar zxvf openssh-5.2p1.tar.gz

 

cd openssh-5.2p1

 

./configure –prefix=/usr –with-pam –with-zlib –sysconfdir=/etc/ssh –with-ssl-dir=/usr –with-md5-passwords

 

make

 

make install

Comments

OpenVZ resource management -CPU share articles

 

Continued yesterday content,OpenVZ today describes how to control CPU resources that can be used VE。OpenVZ resource manager allows VE guarantee of CPU time can be used to implement QoS。in

 

Not set cpulimit,And the absence of other VE competitive CPU resources available,VE obtained outside the setting of minimum guaranteed value,You can also exceed this value,To take advantage of HW CPU resources。

 

one、You can set parameters
OpenVZ using specific arithmetic calculation rules CPU time,The unit of the setpoint is CPU time。This makes it possible to avoid a single CPU and multi-CPU load does not mean,Problems not make full use of resources。
You can set parameters:

Quote
ve0cpuunits:This parameter setting is global configuration file,CPU time defined minimum usable VPS 0,That is the least resources available to ensure that the value of HW。The recommended setting is HW gross CPU time of 5 to 10%;
cpuunits:VE available resources to ensure the minimum CPU time;
cpulimit:The percentage of CPU time must not exceed the VE。

As I mentioned at the beginning,cpuunits not a fixed value,As long as resources permit,In the case does not exceed the percentage of cpulimit,VE can have full access to CPU resources。

two、Setting CPU share
1、The total CPU time calculating HW
first step,Of course, we need to calculate the current VPS 0 (HW) how much CPU time can dominate。

Quote
# vzcpucheck
Current CPU utilization: 1000 #HW start and has been occupied by the CPU time of VE
Power of the node: 85105 #The total number of CPU time HW

2、HW可用CPU time

Quote
# grep ‘VE0CPUUNITS=1000’ /etc/vz/vz.conf
VE0CPUUNITS = 1000

This is the default value,Also did not mean to start before VE,The results obtained running vzcpucheck。

3、VE set of CPU time

# vzctl set 115 –cpuunits 2500 –cpulimit 5 –save

or

Quote
# vi /etc/vz/conf/115.conf
CPUUNITS =”2500″
CPULIMIT =”5″

it means:

Quote
1) CPU full load even in the HW,Or speak,the current CPU utilization等于the power of the Node的情况下,115 VE can get about 3% (2500/85105) of the CPU time resources;
2) But in the case of CPU idle,115 VE and can not get more than 5 percent of the CPU time resources;
3) Is speaking,Under normal circumstances,115 VE resources available CPU time between 3% to 5%;
4) If set cpulimit,So in the absence of other VE 115 VE competition,The lower resource and allow the situation,It can be more than 3%,But as long as no more than HW load on it。

Start VE,result:

Quote
# vzctl start 115
# vzcpucheck
Current CPU utilization: 3500
Power of the node: 85105

This setting is effective or dynamic:

Quote
# vzctl set 115 –cpuunits 4000 –cpulimit 5 –save
Setting CPU limit: 5
Setting CPU units: 4000
Configure meminfo: 49152
Saved parameters for VE 115
# vzcpucheck
Current CPU utilization: 5000
Power of the node: 85105

4、problem
From the above description may know,OpenVZ usually with a minimum guarantee value VE can make full use of system resources,This is one of the design principles。But the result will bring a problem,It is:

Quote
# vzctl set 112 –cpuunits 85000 –cpulimit 5 –save
# vzctl start 112
# vzcpucheck
Current CPU utilization: 105000
Power of the node: 85105
Warning: hardware node is overcommited

just in case,You set a minimum guarantee for all its VE gross CPU time resources available HW greater than the actual CPU time。Then,On issues of CPU overload may occur。When this happens in real,115 VE can not get 3% of the CPU time resources available to its original guarantee,This may cause the entire virtual system error。
of course,This will only happen 112 VE full use of CPU time in,HW case of overload。And in most cases,VE CPU-peak is not at the same time,Dynamically allocated on the OpenVZ,CPU time can get more fully utilized,and so,Only Warning,Instead of Error。But in order to avoid problems,Recommendations or make current CPU utilization equal to the power of the Node better。


Comments

Xen server mount new local hard disk

1、XenCenter console into the server
2、[root@szwj-xenvm01 ~]# fdisk -l to find new hard disk device number (such as:/dev / sdb)
3、[root@szwj-xenvm01 ~]# xe sr-create name-label=”The new hard disk device name” shared = false device-config-device = / dev / sdb type = lvm (/ dev / sdb device number of the new hard disk)

Comments