Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Importance of IOPS, where to look at

b00nb00n Member
edited December 2025 in General

Hi all,

I'm trying to decide whether I should pick provider #2 over provider #1.
I'm happy with the other YABS results, but what I have less feeling with is the impact of the IOPS results between provider #1 and #2.

What kind of performance differences would I see if both YABS results would be the only difference between the two?
Which block-size results are the most important to look at (4k,64k,512k,1m) and why?

Added context: we talk about a VPS/VDS with some calculations being done and a webserver with a low/medium amount of users.

Are Provider #2 results bad, or is provider #1 very good? Don't have a good feeling with these numbers.

Hope you experts could help me out? Thanks

Provider #1

Block Size 4k (IOPS) 64k (IOPS)
Read 275.54 MB/s (68.8k) 3.56 GB/s (55.7k)
Write 276.26 MB/s (69.0k) 3.58 GB/s (56.0k)
Total 551.80 MB/s (137.9k) 7.15 GB/s (111.8k)
Block Size 512k (IOPS) 1m (IOPS)
------ --- ---- ---- ----
Read 8.47 GB/s (16.5k) 10.57 GB/s (10.3k)
Write 8.92 GB/s (17.4k) 11.27 GB/s (11.0k)
Total 17.40 GB/s (33.9k) 21.84 GB/s (21.3k)

Provider #2:

Block Size 4k (IOPS) 64k (IOPS)
Read 181.94 MB/s (45.4k) 1.80 GB/s (28.2k)
Write 182.42 MB/s (45.6k) 1.81 GB/s (28.4k)
Total 364.37 MB/s (91.0k) 3.62 GB/s (56.6k)
Block Size 512k (IOPS) 1m (IOPS)
------ --- ---- ---- ----
Read 5.19 GB/s (10.1k) 5.34 GB/s (5.2k)
Write 5.47 GB/s (10.6k) 5.69 GB/s (5.5k)
Total 10.67 GB/s (20.8k) 11.03 GB/s (10.7k)

Comments

  • allthemtingsallthemtings Member, Megathread Squad

    I dont really understand the post? provider #1 wins in every aspect bigger is better or so they say

    Thanked by 3b00n tux gremeyer
  • b00nb00n Member
    edited December 2025

    @allthemtings said:
    I dont really understand the post? provider #1 wins in every aspect bigger is better or so they say

    Yup and that's why I ask, if course there is a price difference between the two 😁
    What real life differences would I experience. Are Provider #2 results bad, or is provider #1 very good? Don't have a good feeling with these numbers. Will add this to the post, thanks.

  • advinserversadvinservers Member, Patron Provider
    edited December 2025

    To be honest, you probably wouldn't notice a difference between the two. Both results are extremely high and are well beyond what any typical application would consume anyway.

    Choose whichever provider has better CPU performance, pricing, support, or something else.

    In most cases, you should look at 4K IOPS.

  • Have you got a use case in mind? Most applications that don't have a heavy load run okay on hard drives (80-200 IOPS) -- of course with less performance -- so any of these are sufficient -- but sometimes you really need more.

  • b00nb00n Member
    edited December 2025

    @OpaqueRegistrant said:
    Have you got a use case in mind? Most applications that don't have a heavy load run okay on hard drives (80-200 IOPS) -- of course with less performance -- so any of these are sufficient -- but sometimes you really need more.

    It's mostly for downloading some datasets (approx 15GB) every couple of hours, extracting, processing it, then it becomes available on a web server.

Sign In or Register to comment.