VPS / クラウド によって ColoCrossing
仕様
| サーバータイプ | |
|---|---|
| プロセッサー | |
| CPU | 2 @ 2499.998 MHz |
| ストレージ | 36.8 GiB |
| RAM | 1.9 GiB |
| ディストロ |
ランキング
| 指標 | 総合 | 評価 |
|---|---|---|
| 総合スコア | 92.19%上位 | f |
| CPU | 78.25%上位 | d |
| ディスク | 91.02%上位 | f |
| ネットワーク | 79.91%上位 | d |
| レビュー |
|
|
提出の詳細
| ユーザー名 | long1215 |
|---|---|
| バージョン | v2023-11-24 |
| ソース | LowEndTalk |
| 推奨サービス | 該当なし |
| サービス費用 | 該当なし |
| 該当なし |
ISP情報
| ISP | |
|---|---|
| ASN | |
| 組織 | |
| 場所 | |
| 国 |
Clouvider
London, UK (10G)
IPv4
537 Mbits/sec
47.8 Mbits/sec
Scaleway
Paris, FR (10G)
IPv4
busy
busy
NovoServe
North Holland, NL (40G)
IPv4
431 Mbits/sec
97.3 Mbits/sec
Uztelecom
Tashkent, UZ (10G)
IPv4
busy
busy
Clouvider
NYC, NY, US (10G)
IPv4
842 Mbits/sec
83.1 Mbits/sec
Clouvider
Dallas, TX, US (10G)
IPv4
331 Mbits/sec
18.5 Mbits/sec
Clouvider
Los Angeles, CA, US (10G)
IPv4
935 Mbits/sec
783 Mbits/sec
| プロバイダー | 場所 | プロトコル | 送信速度 | 受信速度 | ピング |
|---|---|---|---|---|---|
| Clouvider | London, UK (10G) | IPv4 | 537 Mbits/sec | 47.8 Mbits/sec | 131 ms |
| Scaleway | Paris, FR (10G) | IPv4 | busy | busy | 143 ms |
| NovoServe | North Holland, NL (40G) | IPv4 | 431 Mbits/sec | 97.3 Mbits/sec | 145 ms |
| Uztelecom | Tashkent, UZ (10G) | IPv4 | busy | busy | 270 ms |
| Clouvider | NYC, NY, US (10G) | IPv4 | 842 Mbits/sec | 83.1 Mbits/sec | 62.6 ms |
| Clouvider | Dallas, TX, US (10G) | IPv4 | 331 Mbits/sec | 18.5 Mbits/sec | 144 ms |
| Clouvider | Los Angeles, CA, US (10G) | IPv4 | 935 Mbits/sec | 783 Mbits/sec | 0.561 ms |
生ベンチマークレポート(YABS)
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##</h1>
<h1>Yet-Another-Bench-Script</h1>
<h1>v2023-11-24</h1>
<h1><a href="https://github.com/masonr/yet-another-bench-script" rel="nofollow">https://github.com/masonr/yet-another-bench-script</a></h1>
<h1>## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##</h1>
<p>Sat 25 Nov 2023 09:14:26 AM EST</p>
<h2>Basic System Information:</h2>
<p>Uptime : 0 days, 0 hours, 4 minutes<br />
Processor : Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz<br />
CPU cores : 2 @ 2499.998 MHz<br />
AES-NI : ✔ Enabled<br />
VM-x/AMD-V : ❌ Disabled<br />
RAM : 1.9 GiB<br />
Swap : 2.5 GiB<br />
Disk : 36.8 GiB<br />
Distro : Debian GNU/Linux 11 (bullseye)<br />
Kernel : 5.10.0-23-amd64<br />
VM Type : KVM<br />
IPv4/IPv6 : ✔ Online / ❌ Offline</p>
<h2>IPv4 Network Information:</h2>
<p>ISP : ColoCrossing<br />
ASN : AS36352 ColoCrossing<br />
Host : ColoCrossing<br />
Location : Los Angeles, California (CA)<br />
Country : United States</p>
<h2>fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda1):</h2>
<table>
<thead>
<tr>
<th>Block Size</th>
<th>4k (IOPS)</th>
<th>64k (IOPS)</th>
</tr>
</thead>
<tbody>
<tr>
<td>Read</td>
<td>845.00 KB/s (211)</td>
<td>11.11 MB/s (173)</td>
</tr>
<tr>
<td>Write</td>
<td>884.00 KB/s (221)</td>
<td>11.64 MB/s (181)</td>
</tr>
<tr>
<td>Total</td>
<td>1.72 MB/s (432)</td>
<td>22.76 MB/s (354)</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Block Size</td>
<td>512k (IOPS)</td>
<td>1m (IOPS)</td>
</tr>
<tr>
<td>------</td>
<td>--- ----</td>
<td>---- ----</td>
</tr>
<tr>
<td>Read</td>
<td>70.64 MB/s (137)</td>
<td>135.38 MB/s (132)</td>
</tr>
<tr>
<td>Write</td>
<td>74.39 MB/s (145)</td>
<td>144.40 MB/s (141)</td>
</tr>
<tr>
<td>Total</td>
<td>145.04 MB/s (282)</td>
<td>279.78 MB/s (273)</td>
</tr>
</tbody>
</table>
<h2>iperf3 Network Speed Tests (IPv4):</h2>
<table>
<thead>
<tr>
<th>Provider</th>
<th>Location (Link)</th>
<th>Send Speed</th>
<th>Recv Speed</th>
<th>Ping</th>
</tr>
</thead>
<tbody>
<tr>
<td>Clouvider</td>
<td>London, UK (10G)</td>
<td>537 Mbits/sec</td>
<td>47.8 Mbits/sec</td>
<td>131 ms</td>
</tr>
<tr>
<td>Scaleway</td>
<td>Paris, FR (10G)</td>
<td>busy</td>
<td>busy</td>
<td>143 ms</td>
</tr>
<tr>
<td>NovoServe</td>
<td>North Holland, NL (40G)</td>
<td>431 Mbits/sec</td>
<td>97.3 Mbits/sec</td>
<td>145 ms</td>
</tr>
<tr>
<td>Uztelecom</td>
<td>Tashkent, UZ (10G)</td>
<td>busy</td>
<td>busy</td>
<td>270 ms</td>
</tr>
<tr>
<td>Clouvider</td>
<td>NYC, NY, US (10G)</td>
<td>842 Mbits/sec</td>
<td>83.1 Mbits/sec</td>
<td>62.6 ms</td>
</tr>
<tr>
<td>Clouvider</td>
<td>Dallas, TX, US (10G)</td>
<td>331 Mbits/sec</td>
<td>18.5 Mbits/sec</td>
<td>144 ms</td>
</tr>
<tr>
<td>Clouvider</td>
<td>Los Angeles, CA, US (10G)</td>
<td>935 Mbits/sec</td>
<td>783 Mbits/sec</td>
<td>0.561 ms</td>
</tr>
</tbody>
</table>
<h2>Geekbench 6 Benchmark Test:</h2>
<p>Test | Value<br />
|<br />
Single Core | 507<br />
Multi Core | 914<br />
Full Test | <a href="https://browser.geekbench.com/v6/cpu/3710478" rel="nofollow">https://browser.geekbench.com/v6/cpu/3710478</a></p>
<p>YABS completed in 24 min 8 sec</p>
ColoCrossing の最新ベンチマーク
| Date | User | Location | CPU | Storage | RAM | Score | ||
|---|---|---|---|---|---|---|---|---|
| 04/08/26 | Elk Grove Village, United States | Intel Xeon CPU E5-2683 v4 @ 2.10GHz | 20 GiB | 1 GiB | ||||
| 04/03/26 | Buffalo, United States | Intel Xeon CPU E5-2683 v4 @ 2.10GHz | 29 GiB | 1 GiB | ||||
| 01/31/26 | Buffalo, United States | Intel Xeon CPU E3-1240 v3 @ 3.40GHz | 95 GiB | 32 GiB | ||||
| 01/31/26 | Los Angeles, United States | Intel Xeon CPU E5-2699 v4 @ 2.20GHz | 29 GiB | 1 GiB | ||||
| 01/10/26 | Buffalo, United States | Intel Xeon CPU E5-2683 v4 @ 2.10GHz | 29 GiB | 1 GiB | ||||
| 01/08/26 | Elk Grove Village, United States | Intel Xeon CPU E5-2699 v4 @ 2.20GHz | 29 GiB | 1 GiB | ||||
| 12/29/25 | Los Angeles, United States | Intel Xeon CPU E5-2660 v2 @ 2.20GHz | 59 GiB | 4 GiB | ||||
| 12/08/25 | Los Angeles, United States | Intel Xeon CPU E3-1240 v3 @ 3.40GHz | 334 GiB | 32 GiB | ||||
| 12/05/25 | Los Angeles, United States | Intel Core i7-6700K CPU @ 4.00GHz | 2 TiB | 32 GiB | ||||
| 11/26/25 | Buffalo, United States | Intel Xeon CPU E5-2683 v4 @ 2.10GHz | 39 GiB | 2 GiB |