LiveStreet periodically raises performance issues. Sooner or later, everyone comes to the fact that the usual hosting does not pull the engine due to some of its features. There are exceptions to the rule, but rarely - usually with new hosts with “empty” servers.

A couple of days ago, I said that I had switched to Handi.net, where I tested various software. Unfortunately, the tests were not preserved, and in this article I limited myself to the description of installing software under FreeBSD.

Quite unexpectedly, I received an offer from TrueVDS.ru to write instructions for installing software for Debian for newbies and test some tariff plans. I decided to split the instructions and tests into two posts, because someone is interested in one thing, someone else, but the text has turned out a bit too much, hard for perception. Installing software under Debian here ,
')
Let's start testing with the second line of True20 tariffs, because in the first line there is extremely little memory and it’s problematic to put in there eaccelerator and memcache.

True20 - 480 MHz / 256 Mb

nginx + php-cgi + mysql:

siege with settings: 10 people attack the site for 1 hour in imitation mode of the Internet:

Transactions: 18514 hits
Availability: 100.00 %
Elapsed time: 3600.05 secs
Data transferred: 211.42 MB
Response time: 1.43 secs
Transaction rate: 5.14 trans/sec
Throughput: 0.06 MB/sec
Concurrency: 7.33
Successful transactions: 18514
Failed transactions: 0
Longest transaction: 6.87
Shortest transaction: 0.02

nginx + php-cgi + mysql + eaccelerator:

siege - the settings are the same: 10 people, 1 hour.

Transactions: 53616 hits
Availability: 100.00 %
Elapsed time: 3602.28 secs
Data transferred: 611.88 MB
Response time: 0.16 secs
Transaction rate: 14.88 trans/sec
Throughput: 0.17 MB/sec
Concurrency: 2.38
Successful transactions: 53616
Failed transactions: 0
Longest transaction: 1.80
Shortest transaction: 0.00

nginx + php-cgi + mysql + eaccelerator + memcache:

siege - 10 people, 1 hour.

Transactions: 54468 hits
Availability: 100.00 %
Elapsed time: 3602.58 secs
Data transferred: 622.92 MB
Response time: 0.14 secs
Transaction rate: 15.12 trans/sec
Throughput: 0.17 MB/sec
Concurrency: 2.12
Successful transactions: 54468
Failed transactions: 0
Longest transaction: 1.48
Shortest transaction: 0.00

For comparison, I want to propose to test an identical bundle that is configured on a single ball (1 share) in a handy net. Gandhi is a good hosting, no doubt. But they are cunning. It says:

Processor: 1 / 60th quadri Quad Core AMD + 1 / 60th on reserve

Quad AMD quad-core is a total of 16 cores. If 1 share is 1/60, then it will be ~ 27% of the kernel. Roughly correlating one of their cores with the Intel core of 2.5 GHz, 1/4 of the core will be about 650 MHz versus 480 MHz for truevds. Memory is the same - 256Mb. Siege with the same settings - 10 people and 1 hour. We look:

Transactions: 44040 hits
Availability: 100.00 %
Elapsed time: 3601.48 secs
Data transferred: 127.84 MB
Response time: 0.30 secs
Transaction rate: 12.23 trans/sec
Throughput: 0.04 MB/sec
Concurrency: 3.69
Successful transactions: 44040
Failed transactions: 0
Longest transaction: 5.62
Shortest transaction: 0.01

Gandhi with a more powerful processor lost. What's the matter? We look, what processor costs actually:

/proc/cpuinfo

And we see:

Model name: Dual-Core AMD Opteron (tm) Processor 8218

It turns out that the processor is not 4th, but 2-core. :( Draw your own conclusions.

We turn to heavy artillery. The True30 tariff line starts with 1280 MHz and 1024 Mb of memory. Feel it and feel:

True30 - 1280 MHz / 1024 Mb

nginx + php-cgi + mysql:

siege - 10 people, 1 hour.

Transactions: 44928 hits
Availability: 100.00 %
Elapsed time: 3601.14 secs
Data transferred: 138.96 MB
Response time: 0.28 secs
Transaction rate: 12.48 trans/sec
Throughput: 0.04 MB/sec
Concurrency: 3.55
Successful transactions: 44928
Failed transactions: 0
Longest transaction: 1.62
Shortest transaction: 0.02

nginx + php-cgi + mysql + eaccelerator:

siege - 10 people, 1 hour.

Transactions: 67614 hits
Availability: 100.00 %
Elapsed time: 3602.52 secs
Data transferred: 209.88 MB
Response time: 0.03 secs
Transaction rate: 18.77 trans/sec
Throughput: 0.06 MB/sec
Concurrency: 0.53
Successful transactions: 67614
Failed transactions: 0
Longest transaction: 0.59
Shortest transaction: 0.00

nginx + php-cgi + mysql + eaccelerator + memcache:

siege - 10 people, 1 hour.

Transactions: 68898 hits
Availability: 100.00 %
Elapsed time: 3599.58 secs
Data transferred: 214.80 MB
Response time: 0.03 secs
Transaction rate: 19.14 trans/sec
Throughput: 0.06 MB/sec
Concurrency: 0.55
Successful transactions: 68898
Failed transactions: 0
Longest transaction: 0.49
Shortest transaction: 0.00

nginx + php-cgi + mysql + eaccelerator + memcache:

siege - 30 people, 1 hour.

Transactions: 137886 hits
Availability: 100.00 %
Elapsed time: 3602.16 secs
Data transferred: 428.58 MB
Response time: 0.28 secs
Transaction rate: 38.28 trans/sec
Throughput: 0.12 MB/sec
Concurrency: 10.76
Successful transactions: 137886
Failed transactions: 0
Longest transaction: 1.29
Shortest transaction: 0.00

TOTAL

In my opinion, true20 is quite enough for comfortable work on LiveStreet. If attendance grows so that this tariff “clogs” - there are elder brothers.

True30 is able to keep a good load. If you still optimize the software: mysql, memcache and eaccelerator, the results will be even better.