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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Throwing this out there for a project
I don't exactly know how big this environment will be, but I'll start with a good base:
CPU: 4–6 cores
RAM: 8 GB minimum (more is never turned down; I can always add more later if needed)
OS Drive: A base of 128 GB
Bandwidth: I'll take as much 1 Gbps bandwidth as I can get in the offers—who knows if something becomes a thing.
Next is the storage. It’s going to be a lot of database storage. If there's just 1 TB that can be slapped on as a secondary drive to handle the bulk of the database and backups, that’s fine.
Plan can be monthly, annual, and so on.
I'm more curious what discounts I can get for a more long term.
Comments
Are these resources actually enough to be able to query a DB of several hundred GB in size effectively?
Tbh I have no idea, my DBs are smaller and run on more resources
Honestly ill take a look at any offers
@layer7
6 Shared EPYC Cores
16 GB Ram
120GB NVMe SSD
1TB HDD
50TB BW @ 1G
Frankfurt, Germany
11.99 eur/m
Can get this as VDS too but at higher price. Also available in Paris, France.
Hi,
database usually means that normal HDD wont be fast enough for this.
And 1 TB of SSD/NVMe space that really delivered permanently a high level of speed will be quiet very costy - if available anyway.
So please clarify for yourself how much fast storage you really need. And how much slower storage you would need for backups and other cold-storage related content.
I suggest you to separate both requirements. Otherwise the cost will be very (un)sexy ....
Good luck!
Good points, it might have to be a dedicated server with dual nvme and then a separate server for backups and cold storage.
@irkyo It would be helpful to state budget and preferred region/countries too.
Yes. And one should estimate what indexes it needs for relatively fast queries and how much RAM they’d need to comfortably sit in RAM. This is important for way smaller DBs than hundreds of GB.
What database setup are we talking about and what are its demands?
are they running sqlite,postgresql,mariadb,duckdb. What exactly?
@irkyo if possible, be more specific for your use case in particular.
Here's a lot of storage:
6c / 16GB / 260GB / 8TB is the next plan in this line-up.
NVMe storage VDSes (AMD EPYC) are also available, up to 4 TB.
Selecting annual billing gives you a discount.
/ turn your VPN off before ordering /
Seriously. There are differences between large databases and large databases, heavy use and heavy use. I very very much know, NDA has not expired but I can tell you that I was in a project group where the end procuct is used by more than 1/4 of our country a few years later.
They see some SERIOUS fucking access, but the base itself is puny.
A database at 1 damn TB and it's gonna be under heavy load? You pay low 5 digits to have other people design those. (Poking fun aside; you really really really need to specify this)
Netcup may be an ideal choice.