No, that will be way to slow, and 2GB RAM is also not great. 250MBit is also not exactly fast for file transfer. 2 TB hard-drive is of course nice but you really need that much?
Also SATA vs. SSD: If you have sufficient RAM and can run all the caching & file-locking (Redis etc.) than a normal harddrive might be ok, but still not great. But without that I would definitely recommend a much faster SSD.
I have the RS 1000 (but a slightly older version with only 6 GB ram) and it runs great including some other heavy services like the OnlyOffice Document server (I run it via the Netcup provided Ubuntu18.04 Docker image with Traefik installed and the Nextcloud-Apache / Redis / Postgres Docker images). I have the SSD version, can’t really comment on the SAS and would be also interested how the storage plan would work out with Nextcloud.
Edit: I am pretty sure it would work with 10-15 users, but my current setup has been only tested up to 5 user or so. Was super fast for those 5 though.
How do you think the usage pattern will be?
I am guessing that if your users are syncing a lot of small files all the time, then a SSD will perform better. If not you are probably fine with the SAS offer (if you set up all the caching and file-locking stuff in Nextcloud). But I am really just guessing here.
Users will be uploading files anywhere from 2-50 mb at a time. It’s not going to be a thing where they upload loads of files every minute, every hour or so they will most likely submit their work/files.
Not that much activity to be honest, it’s for a group project to keep all files organised in a central location.
It would be nice to see some sort of graph/visual presentation of the difference but I guess that is difficult as every SAS and SSD drive will have varying speeds.
when you search the netcup forum discussions, you’ll see some positive remarks on the SAS storage. For your scenario this should be the best fit. You should tune your db caches and php cache as documented in the nextcloud installation instructions and you’ll be sure the bottleneck will be your users home / internet connection rather than anything else. You’ll see you have plenty of RAM for cache purposes.
be carefull about all those ovh, 1&1 and others offerts … the MB cost !!!
My first deployement was to have an OVH virtual server for hosting the web server and channeling the users data to an amazon s3 secure space.
Due to some glitch with nc13, i had to rely on ovh for providing a safe space.
Unfortunatly, the object storage is cheap ( 0,01 € HT/mois/Go), but very very slow…
The STOR-XX server are between 110-450 a month !!
I build a debian server with specific hardware ( icy-box, pci cards … ) and bought some hdd to have a 48GO Raid 60 server. The budget and the hosting of this server has been flattened in 14 months …
Sorry, can’t give you a benchmark figure. But I think that would be meaningless anyways as Nextcloud isn’t exactly known for high speed individual file access/download. The real question is how a system behaves in a multi-user simultaneous access scenario, and so far I have heard no / have no complaints about slow access on my system.
I’ve been running Nextcloud for months on a SYS ARM storage server.
ARM-2T Server - Cortex A9 - 2GB - 1x2To
It suits me fine, as a long-term storage server. All that interests me though, are encryption and consistent, predictable storage. I stagger the access, from VPS, so only one client at a time and run a custom kernel that makes better use of the available network speed.
Upload performance, using rsync mirror, through a davfs2 mount:
2,724,863.79 bytes/sec total size is 19,061,399,207 27m41s
(Just for your benefit…) Downloading an 1.8GB ISO, via Nextcloud web interface, to my laptop at home:
It’s a different use case than yours, OP, but may be of interest. Generally, it’s a bit sluggish but it’s not horrendous, by any means.
Honestly, I would go the other way round. SATA storage is much cheaper, with enough RAM the database and caching will make the whole system pretty fast. Not sure if there are so many cases, where you would see the difference with an SSD.
Are you joking? If these 20 users are not constantly syncing very large files with each other, 100 Mbit/s should be largely enough.
I’d check this:
make sure that you run your own system, and that the contract time is very limited, so you can easily change the operator
RAM is probably the most critical resource. The less you have, the better you must manage it. 2 GB is probably a bit short, better is 4 GB. 8 GB give you a bit more operating range. But it also depends what you use Nextcloud for and which features you intend to use
And if it gets too cheap be careful about the conditions, for cloud storage if they limit the number of requests, or if it is paid. With vservers you can start small and easily add resources when needed, however these resources are shared.
If you don’t need a lot of storage, you can get some nice ARM boards here: