Transparent, verified telemetry from VisiHost's Noida VPS compute node. We publish raw Sysbench multi-threaded CPU scores, FIO 4K random read/write storage telemetry, and domestic latency benchmarks across major Indian cities.
In the cloud infrastructure industry, marketing materials are filled with grandiose claims: "lightning-fast processors," "ultra-low latency," and "blazing NVMe speeds." Yet, experienced software engineers and infrastructure architects know that marketing claims are meaningless without verifiable, reproducible telemetry.
When selecting an Indian cloud server for production web applications, database clusters, or latency-sensitive APIs, technical teams require concrete performance numbers: What are the raw multi-threaded CPU event speeds? What is the sustained random 4K read/write IOPS under queue depth 32? What is the actual round-trip network latency to major Indian transit corridors?
To provide complete transparency into our infrastructure, VisiHost conducted comprehensive, multi-hour hardware benchmarks on our production Noida VPS compute nodes. In this report, we publish the raw telemetry from industry-standard benchmarking suites—including Sysbench 1.0.20, FIO 3.36, and network routing telemetry across Delhi NCR and nationwide metros.
All tests documented in this report were executed on a standard, production-grade VisiHost Intel Xeon XS instance provisioned directly from our Noida, Uttar Pradesh data center facility.
virtio driversTo measure raw computational performance, memory bandwidth, and CPU event latency, we utilized Sysbench 1.0.20, the standard Linux system evaluation tool.
The Sysbench CPU test calculates prime numbers up to a maximum value of 20,000, measuring execution time, events per second, and latency distribution percentiles.
bash# Sysbench CPU 2-Thread Test Command sysbench cpu --cpu-max-prime=20000 --threads=2 run
+-------------------------------------------------------------------------+
| SYSBENCH CPU BENCHMARK TELEMETRY |
+---------------------------------+-------------------+-------------------+
| Metric / Parameter | 1 Thread (Single) | 2 Threads (Multi) |
+---------------------------------+-------------------+-------------------+
| Total Events Processed | 10,000 | 10,000 |
| Total Execution Time | 7.2148s | 3.6421s |
| Events Per Second | 1,385.98 / sec | 2,745.36 / sec |
| Latency: Minimum | 0.71 ms | 0.70 ms |
| Latency: Average | 0.72 ms | 0.73 ms |
| Latency: 95th Percentile | 0.73 ms | 0.74 ms |
| Latency: 99th Percentile | 0.75 ms | 0.76 ms |
+---------------------------------+-------------------+-------------------+
Storage throughput and random I/O performance are the primary determinants of database responsiveness (PostgreSQL, MySQL, MongoDB) and application build speeds. We utilized FIO (Flexible I/O Tester) version 3.36 to evaluate our enterprise PCIe NVMe storage arrays.
Random 4K operations simulate the exact disk access patterns of relational databases executing concurrent queries, updating index trees, and appending to write-ahead logs (WAL).
bash# FIO Random 4K Test Command (Direct I/O, Queue Depth 32, 4 Jobs) fio --name=rand4k --ioengine=libaio --iodepth=32 --rw=randrw --rwmixread=75 --bs=4k --direct=1 --size=2G --numjobs=4 --runtime=60 --group_reporting
+-------------------------------------------------------------------------+
| FIO RANDOM 4K READ/WRITE TELEMETRY |
+--------------------------+---------------------+------------------------+
| Metric / Parameter | Read Performance | Write Performance |
+--------------------------+---------------------+------------------------+
| IOPS (IO Operations/Sec) | ~42,800 IOPS | ~14,250 IOPS |
| Bandwidth / Throughput | 171.2 MB/s | 57.0 MB/s |
| Latency: Average | 0.74 ms | 2.24 ms |
| Latency: 95th Percentile | 1.12 ms | 3.85 ms |
| Latency: 99th Percentile | 1.48 ms | 4.92 ms |
+--------------------------+---------------------+------------------------+
| Combined Total IOPS | 57,050 IOPS |
+--------------------------+----------------------------------------------+
Sequential tests measure sustained bandwidth when streaming media, creating database dumps, or extracting large archives.
bash# FIO Sequential 1MB Test Command fio --name=seq1m --ioengine=libaio --iodepth=16 --rw=readwrite --bs=1M --direct=1 --size=4G --numjobs=2 --runtime=30 --group_reporting
Compared to budget hosting providers utilizing legacy SATA SSDs (which cap at ~500 MB/s sequential and 10,000–15,000 IOPS), VisiHost's enterprise PCIe NVMe storage array delivers 3.5x to 4x higher sustained disk throughput. For developers running PostgreSQL or MongoDB, this translates into zero disk bottlenecking during intensive database transactions.
Datacenter placement determines network packet transit times for users across the Indian subcontinent. To measure real-world network responsiveness, we conducted multi-point ICMP ping tests from our Noida compute node to major telecom nodes, regional gateways, and major cities across India.
+-------------------------------------------------------------------------+
| NOIDA VPS REGIONAL LATENCY BENCHMARK |
+--------------------------+---------------------+------------------------+
| Destination City / Hub | Distance from Node | Measured Round-Trip RTT|
+--------------------------+---------------------+------------------------+
| Noida / Greater Noida | Local DC | 1.8 - 2.8 ms |
| New Delhi (Central) | ~25 km | 2.4 - 4.2 ms |
| Gurugram (Haryana) | ~45 km | 3.2 - 5.6 ms |
| Faridabad (Haryana) | ~30 km | 2.9 - 4.8 ms |
| Chandigarh (Punjab) | ~260 km | 8.4 - 12.2 ms |
| Jaipur (Rajasthan) | ~290 km | 9.8 - 14.5 ms |
| Lucknow (UP East) | ~510 km | 10.2 - 15.8 ms |
| Dehradun (Uttarakhand) | ~240 km | 7.8 - 11.4 ms |
| Mumbai (Maharashtra) | ~1,400 km | 22.4 - 26.8 ms |
| Pune (Maharashtra) | ~1,450 km | 24.2 - 28.5 ms |
| Bengaluru (Karnataka) | ~2,150 km | 28.6 - 34.2 ms |
| Hyderabad (Telangana) | ~1,550 km | 26.4 - 31.8 ms |
| Kolkata (West Bengal) | ~1,480 km | 25.1 - 30.4 ms |
| Chennai (Tamil Nadu) | ~2,180 km | 32.2 - 37.5 ms |
+--------------------------+---------------------+------------------------+
Memory throughput directly influences high-concurrency Node.js garbage collection passes, in-memory caching layers (Redis, Memcached), and complex sorting algorithms in databases like PostgreSQL and MySQL.
Using Sysbench's memory benchmark suite, we evaluated both sequential and random memory transfer rates across our ECC Registered DDR4 memory channels:
bash# Sysbench Sequential Memory Transfer Test Command sysbench memory --memory-block-size=1M --memory-total-size=100G --memory-oper=write --memory-access-mode=seq run
+-------------------------------------------------------------------------+
| SYSBENCH MEMORY READ/WRITE TELEMETRY |
+--------------------------+---------------------+------------------------+
| Operation / Access Mode | Total Data Tested | Sustained Throughput |
+--------------------------+---------------------+------------------------+
| Sequential Memory Write | 100,000 MB (100 GB) | 16,842.15 MB/sec |
| Sequential Memory Read | 100,000 MB (100 GB) | 22,410.80 MB/sec |
| Random Memory Write | 50,000 MB (50 GB) | 11,280.45 MB/sec |
| Random Memory Read | 50,000 MB (50 GB) | 14,920.10 MB/sec |
+--------------------------+---------------------+------------------------+
While latency measures packet transit time, throughput measures bandwidth volume. To confirm that our 1 Gbps node ports deliver unthrottled bandwidth under heavy egress load, we ran synthetic iPerf3 bidirectional saturation tests against regional test endpoints:
bash# iPerf3 10-Stream Parallel Uplink Test iperf3 -c speedtest.noida.visihost.in -P 10 -t 30
This confirms that VisiHost instances are connected to genuine gigabit switch fabric with unchoked upstream transit, capable of handling bursty web traffic spikes, large video streaming, or intensive database replication tasks without packet loss.
Synthetic benchmarks that run for 30 seconds can be deceptive; some budget hosts configure aggressive "bursting" algorithms that deliver fast initial numbers but throttle CPU clocks as soon as thermal thresholds are reached.
To test sustained performance under continuous load, we subjected the test instance to a 4-hour continuous stress test utilizing stress-ng:
bash# 4-Hour Sustained Stress Test Command stress-ng --cpu 2 --vm 1 --vm-bytes 4G --timeout 4h --metrics-brief
We encourage developers to verify their hosting infrastructure independently. Below are the open-source commands you can run on any Linux VPS to test CPU, memory, storage, and network performance:
bashsudo apt update && sudo apt install -y sysbench fio curl
bashsysbench cpu --cpu-max-prime=20000 --threads=$(nproc) run
bashfio --name=fio-test --ioengine=libaio --iodepth=32 --rw=randrw --rwmixread=75 --bs=4k --direct=1 --size=1G --numjobs=4 --runtime=30 --group_reporting
bashcurl -sL yabs.sh | bash
The popular YABS (Yet Another Bench Script) suite evaluates CPU performance with Geekbench, disk speed with FIO, and network throughput across global iPerf3 endpoints automatically.
Transparent infrastructure telemetry demonstrates what developers can expect from their hosting provider:
Ready to test this hardware performance for your own applications? Explore Noida VPS hardware and launch your 6GB KVM cloud instance on VisiHost starting at just ₹389/month with domestic UPI payments in INR.
Explore related hosting tutorials, benchmarks, and deployment guides
High-performance infrastructure built for developers, bot creators, and server owners
24/7 no-sleep bot hosting with Pterodactyl panel, DDoS protection and Node.js/Python support.
Full-root cloud VPS with guaranteed resources, NVMe SSD and DDoS protection.
High-performance Minecraft Java & Bedrock servers with Pterodactyl panel.
High-speed managed MongoDB, PostgreSQL & MySQL databases with automated daily backups.
Managed Lavalink nodes for Discord music bots with ultra-low audio latency.
Run your Telegram bots 24/7 with low-latency servers and affordable INR plans.