If vLLM already solved LLM serving, why did SGLang appear?
Updated on
Published on
Table of Content
About the author
For a lot of AI work the RTX 4090 is good enough, but there is a clear point where the 4090 stops working. That point is memory. A 4090 has 24 GB. An H100 has 80 GB.
Almost everything else in this comparison comes back to that one number. If your models and data fit inside 24 GB, the 4090 is the better buy and often the faster card for the money. If they do not, you need an H100, or another card with more memory like the RTX Pro 6000, H200, or B200.
The rest of this goes over where the line falls [aka use 4090 or H100], what each card can and cannot do, what they cost in 2026, and why renting an H100 is generally the right move.
A 4090 is a strong AI card for its price. It runs small and mid-sized language models well. A 7B or 13B model, quantised, will generate text on a 4090 at around 80 to 120 tokens per second, which feels fast and responsive. It is also good for fine-tuning smaller models with QLoRA, up to roughly 20B. And it is one of the best cards you can buy for image generation, handling Stable Diffusion and Flux comfortably.
For a solo developer, a student, or anyone building and testing on their own machine, that covers most of what you would want to do. You can run a local chatbot, fine-tune a model on your own data, generate images, and prototype an app, all on a card that also plays games.
The problem starts when your model is too big to fit in 24 GB.
A large model like Llama 70B needs roughly 140 GB of memory in full precision. Even after you shrink it with 4-bit quantisation, it still needs around 35 to 40 GB. That is more than a single 4090 has, so the model simply will not load. In community tests using llama.cpp, a single 4090 runs out of memory trying to load a 70B model even at 4-bit, while an H100 loads it with room left over for the rest of the workload.
This is the wall, and it is worth being honest about because a lot of articles are not. You cannot quantise your way past it on one card. You cannot optimise your way past it. The memory is either there or it is not. An H100 has 80 GB, which is enough to hold a 70B model and still leave space for the context and the running calculations.
The same limit shows up in three other places:
This is the most common money-saving idea, and it is a good question. Four 4090s give you 96 GB of memory for far less than one H100. So why not do that?
It comes down to how the cards talk to each other. An H100 has a fast link called NVLink that lets multiple cards share data at 900 GB/s. The 4090 has no NVLink at all, so several 4090s can only communicate over the much slower PCIe connection. For training one large model split across cards, that slow connection becomes the bottleneck and performance suffers badly.
This exact question gets asked often. On an r/LocalLLaMA thread titled “Multiple 4090s instead of H100?”, a user named xinranli gave the clearest explanation of why the H100 is worth the money, and it is mostly about memory speed and the link between cards:
“the HBM on a H100 is significantly faster than GDDR6X on a 4090. By significant I mean 2-3x the bandwidth. Memory bandwidth is often a significant bottleneck for both inference and training.”
He also pointed out that the 4090’s strength is built for games, not AI:
“4090 is made for playing video games so it has very strong FP32 compute power… However, in the context of machine learning, people often prefer to drop the precision down to FP16 or lower,”
where the H100 pulls far ahead.
There is one case where stacking 4090s does work, and it is worth knowing. If you are running many separate jobs at once rather than splitting one big model, several cards side by side are fine, and can be good value. Another commenter on the thread, TheApadayo, summed up the difference between the two cards plainly:
“A 4090 is a graphics processor that happens to also be pretty good at matrix multiplication as a consequence of being good at 3D rendering,” while the H100 “is designed from the ground up for fast efficient computation of AI workloads.”
There is also a legal catch that surprises people. NVIDIA’s licence for GeForce cards does not allow them to be used in a commercial data centre. So even if a rack of 4090s performed well enough, a cloud provider or business cannot legally run them that way. This is part of why companies that need scale buy data-center cards instead, and it is why the only place you really see 4090 servers is China, where the H100 cannot be sold and companies build them out of necessity.
Prices have moved a lot, so here are the current numbers.
| RTX 4090 | H100 | |
| Buy new | about $1,600 | about $25,000 to $40,000 |
| Buy used | about $1,100 to $1,400 | about $12,000 to $22,000 |
| Rent in the cloud | about $0.30 to $0.55 per hour | about $2.30 to $3.10 per hour |
Two things are worth knowing about these. First, used H100 prices have dropped about 85% from their 2023 peak, per CloudZero, because the newer Blackwell cards are now shipping and supply has loosened. Second, H100 cloud prices vary wildly between providers, by as much as 23 times, so where you rent matters as much as what you rent. The big general-purpose clouds tend to charge far more than specialist GPU clouds for the same card.
On running cost, a 4090 draws about 450W and costs roughly $50 a month to run flat out at average US electricity rates, so you can keep it under your desk. An H100 draws 700W and needs proper data-center cooling, which is not realistic in a home or office.
For most people the question is not which of these two to buy. A 4090 is cheap enough to own, and an H100 is expensive enough that you usually want to rent it only when a job needs it. The two cards end up playing different roles rather than competing.
If you are a solo developer or a student, buy a 4090. It does everything local development asks of it, and at a few thousand hours of use it works out cheaper than renting the same card in the cloud.
If you are at a startup or shipping a product, the usual setup is a 4090 on your own machine for everyday work, plus rented H100s in the cloud for the heavy jobs like training or serving a large model. Buying an H100 outright rarely makes sense early on, because $25,000 of hardware sits idle between jobs. Owning one only starts to beat renting once the card is busy almost all the time, roughly more than 70% of the time over a year or more.
So the rule of thumb is simple. For small models, local work, image generation, or learning, buy a 4090. For large models, training at scale, or production serving, rent an H100 by the hour, and buy your own only once it is busy enough to pay for itself.
One more thing worth knowing if you do need a data-center card. The H100 is no longer the top one. The H200, B200, and B300 now sit above it, with more memory and newer features. The H200 in particular has 141 GB of memory, which helps a lot for large models and long context where the H100’s 80 GB runs out. If you are weighing those two, our H100 vs H200 guide goes through it.
That does not make the H100 a bad choice. It has become the cheapest and most proven data-center card rather than the fastest, which makes it good value for anything that fits in 80 GB. You just no longer have to assume it is the only or best option for serious work.
The easiest way to use an H100 or H200 is to rent it, which avoids buying the hardware and dealing with power and cooling. For local work, a 4090 on your own machine is fine and cheap.
For teams in India, or anyone who needs their compute and data to stay in the country, Neysa Velocis rents data-center GPUs hosted in India, including the H100 and H200, along with AMD’s MI300X, and bills with no extra charge for data going in or out or for inference. For regulated work like banking or healthcare, its Aegis layer adds security checks on each request. You can see what is available on the GPU cloud page, and the current rates are on the pricing page.
A 4090 is enough for small and mid-sized models, fine-tuning smaller models, image generation, and local development, and for that work it is the better value by a wide margin. You need an H100 once your model is too big for 24 GB, which in practice means 70B-class models, serious training, or serving lots of users at once. And for most people, the smart setup is to buy a 4090 for everyday work and rent an H100 only when a job actually needs it.

Before you begin:For most AI teams, the NVIDIA H200 remains the safer and more operationally efficient choice. This is why GPU selection should be evaluated within the full AI tech stack, not only through peak specification sheets. AMD’s MI300X becomes compelling primarily for very large-model inference workloads where memory capacity is the bottleneck and teams […]

H200 represented the final evolution of the Hopper generation. It retained the GH100 architecture used in H100 while expanding memory capacity and bandwidth to 141 GB HBM3e at 4.8 TB/s. That additional memory headroom mattered because it enabled practical deployment of larger models: GB300 belongs to a different infrastructure category entirely. It introduces: From a […]

The NVIDIA H100 and A100 have two generations between them, and yet they remain the two cards most Indian AI teams actually weigh when renting compute in 2026. The newest Blackwell parts get the headlines, but the actual budget decision on the ground is still H100 against A100. This is a practical walk-through of that […]