本次测试腾讯云S3.SMALL2实例
配置
- 1核
- 2GB
- 200Mbps
使用体验
腾讯的200M带宽确实没有阿里云来的实在，总是差了点意思，速度上不去。
基准测试
sysbench
–test=cpu –threads=10
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2) Running the test with following options: Number of threads: 10 Initializing random number generator from current time Prime numbers limit: 10000 Initializing worker threads... Threads started! CPU speed: events per second: 947.62 General statistics: total time: 10.0046s total number of events: 9482 Latency (ms): min: 1.04 avg: 10.53 max: 52.11 95th percentile: 36.89 sum: 99838.93 Threads fairness: events (avg/stddev): 948.2000/0.60 execution time (avg/stddev): 9.9839/0.02 |
–test=memory –threads=10
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 |
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2) Running the test with following options: Number of threads: 10 Initializing random number generator from current time Running memory speed test with the following options: block size: 1KiB total size: 102400MiB operation: write scope: global Initializing worker threads... Threads started! Total operations: 38705695 (3869874.61 per second) 37798.53 MiB transferred (3779.17 MiB/sec) General statistics: total time: 10.0002s total number of events: 38705695 Latency (ms): min: 0.00 avg: 0.00 max: 44.03 95th percentile: 0.00 sum: 42053.80 Threads fairness: events (avg/stddev): 3870569.5000/6048.61 execution time (avg/stddev): 4.2054/0.29 |
–test=fileio –threads=10 –file-test-mode=seqwr
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2) Running the test with following options: Number of threads: 10 Initializing random number generator from current time Extra file open flags: (none) 128 files, 16MiB each 2GiB total file size Block size 16KiB Periodic FSYNC enabled, calling fsync() each 100 requests. Calling fsync() at the end of test, Enabled. Using synchronous I/O mode Doing sequential write (creation) test Initializing worker threads... Threads started! File operations: reads/s: 0.00 writes/s: 6454.75 fsyncs/s: 8383.92 Throughput: read, MiB/s: 0.00 written, MiB/s: 100.86 General statistics: total time: 10.0530s total number of events: 147917 Latency (ms): min: 0.01 avg: 0.68 max: 59.32 95th percentile: 2.86 sum: 99896.48 Threads fairness: events (avg/stddev): 14791.7000/315.28 execution time (avg/stddev): 9.9896/0.00 |
bench.sh
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
---------------------------------------------------------------------- CPU model : Intel(R) Xeon(R) Gold 6133 CPU @ 2.50GHz Number of cores : 1 CPU frequency : 2494.144 MHz Total size of Disk : 50.0 GB (2.0 GB Used) Total amount of Mem : 1867 MB (208 MB Used) Total amount of Swap : 0 MB (0 MB Used) System uptime : 0 days, 18 hour 19 min Load average : 0.00, 0.00, 0.00 OS : Debian GNU/Linux 10 Arch : x86_64 (64 Bit) Kernel : 4.19.0-11-amd64 ---------------------------------------------------------------------- |
nench.sh
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
------------------------------------------------- nench.sh v2019.07.20 -- https://git.io/nench.sh benchmark timestamp: 2021-03-17 11:24:00 UTC ------------------------------------------------- Processor: Intel(R) Xeon(R) Gold 6133 CPU @ 2.50GHz CPU cores: 1 Frequency: 2494.144 MHz RAM: 1.8Gi Swap: - Kernel: Linux 4.19.0-11-amd64 x86_64 Disks: vda 50G HDD CPU: SHA256-hashing 500 MB 3.139 seconds CPU: bzip2-compressing 500 MB 5.326 seconds CPU: AES-encrypting 500 MB 1.274 seconds ioping: seek rate ioping: sequential read speed dd: sequential write speed 1st run: 113.49 MiB/s 2nd run: 54.93 MiB/s 3rd run: 99.18 MiB/s average: 89.20 MiB/s |
Speedtest
|
1 2 3 |
Hosted by China Unicom HeNan 5G (Zhengzhou) [9.32 km]: 26.527 ms Testing download speed................................................................................ Download: 177.52 Mbit/s |
There are no comments yet