8 Dedicated x86 64bit Cores
32GB Memory
50GB SSD Disk
250GB Direct SSD Disk
1 Flexible public IPv4
800Mbit/s Unmetered bandwidth
5Gbit/s Internal bandwidth
8 Dedicated x86 64bit Cores
32GB Memory
50GB SSD Disk
250GB Direct SSD Disk
1 Flexible public IPv4
800Mbit/s Unmetered bandwidth
5Gbit/s Internal bandwidth
Well⊠it all depends on what your app does, so itâs difficult to say.
An âhello worldâ would be pretty performant on such a server.
What if a OKCupid clone instead of a âhello worldâ is run on it?
Depends once again what you mean, I donât think the application server would have to do most of the job. Get yourself big hunky servers for the databases. And if you expect a huge number of regular users throughout ten timezones, buy yourself one or two datacenters per continents.
Thank You!
What if the app will have only 2000 to 3000 users online at a time at its peak load, not as many as the real OKCupid have?
Will it hold all of the load on (the said) single dedicated server?
no. never rely on a sole server.
I canât see what the OKCupid site offers so donât know what its needs might be, however I would say if designed and coded well, a Phoenix app on a dedicated server will take quite a lot load - and in some cases, significantly more in comparison to many other languages or frameworks.
The great thing is that dedicated servers are far cheaper than âhosting in the cloudâ, so if you outgrow one, it should not be prohibitive to add another.
I would say if budget is an issue, just go for it! If you outgrow a server you can always add more later - and youâll be surprised by how well a single (relatively beefy) server performs.
I would however stress the importance of making sure you do off-server back ups, and to have two HDs set up in a raid array (so if one fails your app wonât go down).
Elixir is a top performer probably beaten only by C / C++, you have to put it on the test and see how it does, add hardware if needed. Even on a limited resource shared VPS it very fast.
That seems unreasonably optimistic.
Edit: Elixir is fast, but there are plenty of things that are faster.
I think maybe @Neurofunk was urging for more than one server for the same reason as you urged for RAID arrays & backups: Redundancy and potential for zero-downtime.
Itâs not usually a super productive discussion, but I think it depends on what you mean by âfasterâ. Average latency is one metric I expect to see good things in from anything running on the BEAM. Itâs made for handling thousands of things âfast enough for eachâ, so I donât think itâs unreasonable to say that it might beat most in that category.
The great thing is that dedicated servers are far cheaper than âhosting in
the cloudâ,
I would say thatâs exactly backwards until you hit significant scale.
⊠so if you outgrow one, it should not be prohibitive to add another.
And if you over-bought? In my experience most people wildly
overestimate their requirements, and if you own it you canât
easily downgrade to a more appropriate config as you can with
cloud-based servers.
OTOH, if you start with the smallest system that will run your app
you can build up a performance profile and upgrade when and if
it makes sense.
Neurofunk:
no. never rely on a sole server.
YMMV,
Yep - I guess it depends on how quickly you can commission a new server / how much down-time you can afford. However I would still say the same - if budget does not allow it, just do it. In many non-critical applications, being down for a few hours or a day shouldnât be too much of an issue. Itâs like @hassan says below - I think itâs better than overspending.
I was going by the OPâs 2,000 to 3,000 online users, where I think a dedicated box would be cheaper. Having said that, dedicated servers have come down quite a bit in recent years so I donât imagine the difference to be as significant as some might think (unless your app is pretty small).
It would simply mean switching to a different (cheaper server). Most rental contracts are month by month. I wouldnât buy a server (i.e. co-locate) unless I needed more than 10 servers.
_For anyone interested, there are some good recommendations (and further discussion) on dedicated servers in this thread: https://elixirforum.com/t/deploying-elixir-opinions-on-heroku-digitalocean-bluemix-etc/289_
The said server costs only $29 at scaleway.
I donât think Iâve heard of them - but Iâd definitely recommend looking at the thread I posted as I believe quite a few recommendations are in there (and a few other threads weâve had on the topic)
I think Phoenix should easily handle that much load on the said server.
Scaleway is quite cheaper than the options you said in that post. https://www.scaleway.com/baremetal-cloud-servers/
If You plan to have a huge application, then it would be a good idea to think distribution from the start. That way, You will benefit from one of Erlang/Elixir main functionality.
You wonât need to think if your server is big enough, because You could just add one if needed.
Distribution is hard, but mastering it solve scaling problem.
Iâve not heard of them before and tbh, their configuration seems a bit odd - 50GB SSD and a â250GB Direct SSD Diskâ - whatâs a âdirectâ SSD? It just seems a bit odd. Iâd read some reviews and post on webhostingtalk.com for thoughts from other users.
Or look at the dedicated servers from the other companies posted in that thread I linked to
I am not very good at distribution. Is there some book/tutorial etc on how to deploy Phoenix in a distributed way, say deploying it on 4 smaller dedicated servers.