ntdrt Posted June 4, 2014 Report Share Posted June 4, 2014 Zajímalo by mě, jak jsou na tom různí poskytovatelé s výkonem. Zejména u VPS se to nedá prakticky odhadnout. Určitě to chce používat stejný nástroj a parametry, aby se dal výsledek aspoň trochu srovnat, taky by bylo dobrý napsat konfiguraci (velikost ram, velikost hdd, počet jader) + hosting + cenu + virtualizaci. Čím testovat? Já používám sysbench, umí toho testovat hodně a zatím mě fungoval všude. Nainstalovat se dá jednoduše apt-get install sysbench či aptitude install sysbench či yum install sysbench Testování CPU: sysbench --test=cpu --cpu-max-prime=20000 run Úmyslně se testuje výkon jednoho jádra, aby se dali porovnat různé sestavy. Testování HDD: Nejdřív je potřeba vytvořit testovací soubory - musí být větší než operační paměť, aby se vyhnulo kešování - já používám velikost ram + 1GB, třeba... sysbench --test=fileio --file-total-size=10G prepare Potom provedem samotný test (musíte uvést použitou velikost) sysbench --test=fileio --file-total-size=10G --file-test-mode=rndrw --init-rng=on --max-time=300 --max-requests=0 run A po testu smažeme testovací soubory (zase uvedeme použitou velikost) sysbench --test=fileio --file-total-size=10G cleanup odysey 1 Quote Link to comment Share on other sites More sharing options...
ntdrt Posted June 4, 2014 Author Report Share Posted June 4, 2014 Testy: Wedos - 1GB, 1 jádro, 15GB HDD, KVM sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 52.9368s total number of events: 10000 total time taken by event execution: 52.9276 per-request statistics: min: 4.78ms avg: 5.29ms max: 17.57ms approx. 95 percentile: 5.96ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 52.9276/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 16Mb each 2Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 35007 Read, 23338 Write, 74624 Other = 132969 Total Read 546.98Mb Written 364.66Mb Total transferred 911.64Mb (3.0388Mb/sec) 194.48 Requests/sec executed Test execution summary: total time: 300.0035s total number of events: 58345 total time taken by event execution: 192.5880 per-request statistics: min: 0.01ms avg: 3.30ms max: 1043.35ms approx. 95 percentile: 12.50ms Threads fairness: events (avg/stddev): 58345.0000/0.00 execution time (avg/stddev): 192.5880/0.00 Wedos - 2GB, 1 jádro, 30GB HDD, KVM sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 36.4378s total number of events: 10000 total time taken by event execution: 36.4333 per-request statistics: min: 3.36ms avg: 3.64ms max: 21.69ms approx. 95 percentile: 4.54ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 36.4333/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 24Mb each 3Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 11942 Read, 7961 Write, 25472 Other = 45375 Total Read 186.59Mb Written 124.39Mb Total transferred 310.98Mb (1.0365Mb/sec) 66.33 Requests/sec executed Test execution summary: total time: 300.0430s total number of events: 19903 total time taken by event execution: 179.8353 per-request statistics: min: 0.01ms avg: 9.04ms max: 4230.56ms approx. 95 percentile: 34.02ms Threads fairness: events (avg/stddev): 19903.0000/0.00 execution time (avg/stddev): 179.8353/0.00 Wedos - 4GB, 2 jádra, 60GB HDD, KVM sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 49.3054s total number of events: 10000 total time taken by event execution: 49.2994 per-request statistics: min: 4.77ms avg: 4.93ms max: 12.13ms approx. 95 percentile: 5.17ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 49.2994/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 40Mb each 5Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 69824 Read, 46549 Write, 148864 Other = 265237 Total Read 1.0654Gb Written 727.33Mb Total transferred 1.7757Gb (6.0609Mb/sec) 387.90 Requests/sec executed Test execution summary: total time: 300.0077s total number of events: 116373 total time taken by event execution: 208.6520 per-request statistics: min: 0.01ms avg: 1.79ms max: 616.56ms approx. 95 percentile: 11.40ms Threads fairness: events (avg/stddev): 116373.0000/0.00 execution time (avg/stddev): 208.6520/0.00 INIZ (Amsterdam) - 256MB, 2 jádra, 25GB HDD, OpenVZ sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! sysbench --test=cpu --cpu-max-prime=20000 run Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 49.0523s total number of events: 10000 total time taken by event execution: 49.0439 per-request statistics: min: 4.31ms avg: 4.90ms max: 15.14ms approx. 95 percentile: 5.92ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 49.0439/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 8Mb each 1Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 704580 Read, 469720 Write, 1503089 Other = 2677389 Total Read 10.751Gb Written 7.1674Gb Total transferred 17.918Gb (61.158Mb/sec) 3914.09 Requests/sec executed Test execution summary: total time: 300.0184s total number of events: 1174300 total time taken by event execution: 227.6400 per-request statistics: min: 0.00ms avg: 0.19ms max: 2011.24ms approx. 95 percentile: 0.07ms Threads fairness: events (avg/stddev): 1174300.0000/0.00 execution time (avg/stddev): 227.6400/0.00 INIZ (New York) - 256MB, 1 jádro, 20GB HDD, OpenVZ sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 40.7714s total number of events: 10000 total time taken by event execution: 40.7686 per-request statistics: min: 4.01ms avg: 4.08ms max: 5.57ms approx. 95 percentile: 4.25ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 40.7686/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 8Mb each 1Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 37704 Read, 25136 Write, 80384 Other = 143224 Total Read 589.12Mb Written 392.75Mb Total transferred 981.88Mb (3.2729Mb/sec) 209.46 Requests/sec executed Test execution summary: total time: 300.0048s total number of events: 62840 total time taken by event execution: 291.6660 per-request statistics: min: 0.00ms avg: 4.64ms max: 6416.29ms approx. 95 percentile: 14.58ms Threads fairness: events (avg/stddev): 62840.0000/0.00 execution time (avg/stddev): 291.6660/0.00 OVH Classic VPS - 1GB, 1 jádro, 10GB HDD, OpenVZ sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 17.7278s total number of events: 10000 total time taken by event execution: 17.7246 per-request statistics: min: 1.72ms avg: 1.77ms max: 3.83ms approx. 95 percentile: 1.85ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 17.7246/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 16Mb each 2Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 581400 Read, 387600 Write, 1240199 Other = 2209199 Total Read 8.8715Gb Written 5.9143Gb Total transferred 14.786Gb (50.468Mb/sec) 3229.96 Requests/sec executed Test execution summary: total time: 300.0034s total number of events: 969000 total time taken by event execution: 17.0924 per-request statistics: min: 0.00ms avg: 0.02ms max: 139.38ms approx. 95 percentile: 0.02ms Threads fairness: events (avg/stddev): 969000.0000/0.00 execution time (avg/stddev): 17.0924/0.00 Kimsufi - 8GB, 4 jádra, 1TB HDD, dedikovaný sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 25.3691s total number of events: 10000 total time taken by event execution: 25.3685 per-request statistics: min: 2.47ms avg: 2.54ms max: 5.13ms approx. 95 percentile: 2.53ms Threads fairness: events (avg/stddev): 10000.0000/0.00 execution time (avg/stddev): 25.3685/0.00 sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 1 Initializing random number generator from timer. Extra file open flags: 0 128 files, 72Mb each 9Gb total file size Block size 16Kb Number of random requests for random IO: 0 Read/Write ratio for combined random IO test: 1.50 Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing random r/w test Threads started! Time limit exceeded, exiting... Done. Operations performed: 9600 Read, 6400 Write, 20393 Other = 36393 Total Read 150Mb Written 100Mb Total transferred 250Mb (851.98Kb/sec) 53.25 Requests/sec executed Test execution summary: total time: 300.4777s total number of events: 16000 total time taken by event execution: 34.3228 per-request statistics: min: 0.00ms avg: 2.15ms max: 1540.20ms approx. 95 percentile: 10.03ms Threads fairness: events (avg/stddev): 16000.0000/0.00 execution time (avg/stddev): 34.3228/0.00 Výsledek: Wedos - 1GB, 1 jádro, 15GB HDD, KVM - 52s / 3Mb/s Wedos - 2GB, 1 jádro, 30GB HDD, KVM - 36s / 1MB/s Wedos - 4GB, 2 jádra, 60GB HDD, KVM - 50s / 6MB/S INIZ (Amsterdam) - 256MB, 2 jádra, 25GB HDD, OpenVZ - 50s / 60Mb/s INIZ (New York) - 256MB, 1 jádro, 20GB HDD, OpenVZ - 40s / 3Mb/s OVH Classic VPS - 1GB, 1 jádro, 10GB HDD, OpenVZ - 17s / 50Mb/s Kimsufi - 8GB, 4 jádra, 1TB HDD, dedikovaný - 25s / 0,8Mb/s Zkušenosti: Wedos je jeden z nejlepších českých poskytovatelů, ceny nejsou vysoké, profi zázemí. Garance není žádná, reálně se problém řeší v řádě desítkách minut až hodin. Plnohodnotná virtualizace s možností připojení přes VNC. Česká podpora. Traffic se vůbec neomezuje. Slušné webové rozhraní. Výkon průměrný, dostupnost slušná, pro hostování v ČR jedna z nejlepších možností. INIZ má několik datacenter, ceny normálně vyšší než u wedosu, ale dá se sehnat sleva (http://lowendtalk.com/) např. 70%. U OpenVZ verze není možnost VNC/KVM, server se dá jen restartovat/přeinstalovat z image. Není to plnohodnotná virtualizace. Garance žádná, výpadek se řeší v řádů desítek minut až hodin. Přisně omezen traffic. Slušné webové rozhraní (nic nechybí, monitoring). Výkon je slušný (možnost mít SSD), ale díky ceně se větší VPS moc nevyplatí. Špatně se opravuje vážnější problém. OVH je jeden z největších hostingů na světě, mnoho datacenter v zahraniční, česká podpora. VPS classic má opravdu nízkou cenu s garanci SLA 99,98 a zásahu do 10-ti minut. Traffic omezen na 10TB - což by mělo vždycky stačit. Je možnost KVM konzole přes web. Kvalitní webové rozhraní. Hodně dobrá dostupnost, dobrá cena, zatím jsem lepší nabídku neviděl. Výkon je víc než slušný. Kimsufi jsou velice levné dedikované servery, tomu ale odpovídá kvalita - podpora žádná, zásah v řádech dnů, bez KVM - možnost nabootovat "rescue mode", tj. boot ze sítě - lze tak opravit server, ale nevidíte boot, Omezené možnosti debugování, nutnost vypnout server při zásahu. Nehodí se na žádné seriózní projekty, vhodné na nějaké pokusy, kde výpadek nevadí. HW ve špatném stavu - vyběhané nekvalitní disky atp. Zajímavost V testu CPU vyšel nejlíp VPS od OVH, kde se jako na jedinym serveru používá procesor od AMD - AMD Opteron Processor 4386 (3099.999 MHz) odysey 1 Quote Link to comment Share on other sites More sharing options...
matko1213 Posted May 22, 2020 Report Share Posted May 22, 2020 Ja som hostoval svoj web Vosveteit.sk na VPS u websupporte. Tam mi to neustale padalo a bol s tym problem. Neskor som presiel k forpsi, kde maju dvakrat tak vykonny stroj za 50% ceny. tak odporucam pozriet skor tam Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.