March, United Kingdom
Server infrastructure for Genomics in March
Most Genomics outgrow their first server in one specific place — and it is rarely the one the plan name suggests. For a small Genomics business in March that is about 4 Cores, 48 GB of memory and 3000 GB of storage on VDS.
- ✓ 5 infrastructure tiers
- ✓ Sized for your workload, not a plan name
- ✓ Same price in all 24 locations
Estimated from fibre distance, not measured from March. Your real figure depends on your connection and route, and lands inside this range.
Choose the infrastructure for your workload
Three sizes of business, each sized from an assumed traffic figure rather than a measured one. If you know your own numbers, tell us and the estimate changes with them.
Small Genomics Most likely here
1–10 people · ~5,000 visits a month
$803.65 USD USD
per month · VDS
- 4 Cores
- 48 GB RAM
- 3000 GB storage
- GPU on request
About 0.1 requests a second at peak, holding roughly 44.8 GB of working data.
Configure this build →Medium Genomics
11–50 people · ~50,000 visits a month
$2,140.15 USD USD
per month · Dedicated Server
- 16 Cores
- 196 GB RAM
- 4000 GB storage
- Managed
- GPU on request
About 0.5 requests a second at peak, holding roughly 128 GB of working data.
Configure this build →Large Genomics
51+ people · ~500,000 visits a month
$4,549.90 USD USD
per month · Bare Metal
- 32 Cores
- 512 GB RAM
- 4000 GB storage
- Managed
- GPU on request
About 4.6 requests a second at peak, holding roughly 512 GB of working data.
Configure this build →These figures are assumptions stated out loud, not predictions about your business. Memory, cores and disk can all be raised on the same server later, usually within the hour, with no rebuild and no new IP address — so starting one size below the estimate is normally the cheaper mistake.
Why Genomics size up this way
Working from about 5,000 visits a month and roughly 2,667 requests a day, storage grows by roughly 175 GB a month at this size, which usually decides the build before CPU does; about 45 GB of data needs to stay in memory to keep queries fast; and each request costs real computation rather than a cache lookup, so cores matter more here than on a typical site.
- 0.1 req/sec at peak
- 44.8 GB working set
- 175 GB/month growth
- Linux
Which tiers suit Genomics
Including the ones that do not, and why — that is usually the more useful half.
| Infrastructure | Verdict | Why |
|---|---|---|
| Shared Hosting Managed space on a shared server | Not this one | There is no version of this workload that fits on shared hosting. |
| VPS Flexible virtual infrastructure with full root access | Workable | Useful for development, notebooks and light inference, but not for training or sustained compute. |
| VDS Virtual server with resources pinned to you alone | Workable | Suits CPU-bound preprocessing and data preparation with a guaranteed share of the machine. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | Production compute wants the whole machine, with memory bandwidth that is not being shared. |
| Bare Metal Physical compute for sustained, demanding workloads | Recommended | Training, inference and simulation belong on physical hardware, with GPUs available on request. |
Genomics workloads you can host
A single run produces enormous files and the pipeline is CPU-bound for hours — this is batch compute, not a web workload.
- Sequence alignment
- Variant calling pipelines
- Reference genome storage
- Batch job scheduling
- Results archive
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
March is closest to London. Every marker costs the same per month.
Show all 24 locations and distances from March ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Europe, Middle East & Africa · 8 locations | ||
| London, United Kingdom | 73 miles | 2–4 ms |
| Amsterdam, The Netherlands | 203 miles | 5–10 ms |
| Frankfurt, Germany | 407 miles | 10–20 ms |
| Milan, Italy | 639 miles | 15–31 ms |
| Stockholm, Sweden | 835 miles | 20–40 ms |
| Madrid, Spain | 857 miles | 21–41 ms |
| Bucharest, Romania | 1,307 miles | 32–63 ms |
| Tel Aviv, Israel | 2,232 miles | 54–108 ms |
| Americas · 9 locations | ||
| New York, United States | 3,448 miles | 83–166 ms |
| Toronto, Canada | 3,528 miles | 85–170 ms |
| Chicago, United States | 3,922 miles | 95–189 ms |
| Atlanta, United States | 4,192 miles | 101–202 ms |
| Miami, United States | 4,426 miles | 107–214 ms |
| Dallas, United States | 4,724 miles | 114–228 ms |
| Seattle, United States | 4,733 miles | 114–229 ms |
| Santa Clara, United States | 5,319 miles | 128–257 ms |
| Los Angeles, United States | 5,399 miles | 130–261 ms |
| Asia-Pacific · 7 locations | ||
| Delhi NCR, India | 4,161 miles | 100–201 ms |
| Mumbai, India | 4,461 miles | 108–215 ms |
| Kolkata, India | 4,922 miles | 119–238 ms |
| Tokyo, Japan | 5,873 miles | 142–284 ms |
| Hong Kong, China | 5,933 miles | 143–286 ms |
| Singapore | 6,717 miles | 162–324 ms |
| Sydney, Australia | 10,516 miles | 254–508 ms |
Distances are from March. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Genomics in March
The closest of our 24 data centres to March is London, about 73 miles away. Every kilometre between your users and the server is latency you cannot optimise away in software.
March has a population of about 21,051, which is why the small build above is the one most likely to fit a Genomics business here — though the other two are a click away if it does not. Local time is Europe/London, so routine maintenance and backups are scheduled against your overnight rather than ours.
Data stays in the jurisdiction you choose, which matters if you are working to the UK GDPR and the Data Protection Act 2018. Pricing is quoted in GBP, and the figure is the same wherever the machine physically sits.
Network reach from March
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from March | Estimated round trip |
|---|---|---|
| Londonemea | 73 miles | 2–4 ms |
| Amsterdamemea | 203 miles | 5–10 ms |
| Frankfurtemea | 407 miles | 10–20 ms |
March sits in England, and every one of our 24 locations costs the same — so the only thing worth optimising is which of them your users are closest to. At the small size assumed above, that is roughly 2,667 requests a day crossing that link.
Genomics hosting in March — FAQs
What size server does a Genomics business in March, England need?
Where would the server for my March, England business actually run?
Is a VPS enough for Genomics, or do we need a dedicated server?
Can you host sequence alignment for us?
Can we start smaller and grow?
Other industries in March
Same city, different workload.
Genomics hosting nearby
The same workload, in the nearest cities.