1

Topic: Very bad VPS

I need to show that at a hosting of the provider of very bad VPS and consequently the website wildly brakes. At first I write so: dd if =/dev/zero of=___ bs=64k count=16k conv=fdatasync I Receive speed 152 MB/s all would Seem well, but here I write on PHP here so further: <? php $file = ' test.txt '; $start = microtime (true); for ($i = 0; $i <10000; $i ++) {$f = fopen ($file, ' r '); if ($f) {fclose ($f);} } print (microtime (true) - $start); I Receive execution time in some seconds. Note, I do not read any byte, simply I open and I close a file. That the hosting to me did not tell it about restriction on I/O. I need to show that it is such bad VPS at hosting the provider. In difference from not true adjustments Apache or php.ini I Write on  here so: for i in {0. 10000. 1} do value = $ (<test.txt) done Works even longer. A file test.txt in the size 10. Still tried to create a virtual disk: mount-t tmpfs-o size=256M, mode=0777 tmpfs __ to Put the test.txt on it and once again to launch the tests. All the same very long works. For comparing - mine PHP a script  on bluehost shared a hosting for 0.12 seconds. Prompt any unpretentious script to which could demonstrate that VPS very bad. For example that unnaturally long there is a file open operation on reading.

2

Re: Very bad VPS

Hello, tester1917, you wrote: T> I need to show that at a hosting of the provider of very bad VPS It to show very simply. It is necessary to write them the letter, "expensive provider, I close with you the contract, because at you very bad VPS. I ask you to return not spent residual of means". And to move to other provider.

3

Re: Very bad VPS

Hello, tester1917, you wrote: T> I need to show that at a hosting of the provider of very bad VPS T> and consequently the website wildly brakes. You would clarify is better, why the site actually brakes. You that, at handling of one request open ten thousand files? P.S. If you want to measure I/O latency, is ioping. But in itself it about what does not speak.