Gigalixir: Platform-as-a-Service designed just for Elixir/Phoenix

deployment
Tags: #<Tag:0x00007f494024dc28>

#61

Hello @jesse,
I just want to know if the $10 plan Postgres has a size limitation? :slight_smile:


#62

@saint Here is some information about Gigalixir database pricing. http://gigalixir.readthedocs.io/en/latest/main.html#database-sizes-pricing

The free database is a Google Cloud Platform db-f1-micro postgres instance described here, but with a 10,000 row limit. https://cloud.google.com/sql/docs/postgres/pricing


#63

@saint I realized I didn’t actually answer your question. The free plan has a 10,000 row limitation, but the $10 (Standard) plan has no limits.


#64

thanks sir :slight_smile:


#65

Is it possible to use the platform in other GCP regions?


#66

Not at the moment, but we’re planning to expand to other regions based on demand so definitely let me know what region you are looking for.


#67

Does gigalixir provide outgoing internet connection? If so, what is the price? Sorry I failed to find info about it.


#68

@jackalcooper bandwidth is free. So is CPU and disk. You only pay for memory.


#69

Hmm, really? This may raise my tossing it’s name around to people…


#70

I would be guessing there are some hard limits on that free CPU though?


#71

Of course :slight_smile: you get one CPU share for every GB of memory. For more see https://gigalixir.readthedocs.io/en/latest/main.html#replica-sizing

Perhaps a better way to say it is CPU is included when you buy memory.

Bandwidth on the other hand is not capped.


#72

A bit confused on pricing so 1GB RAM with 1 Core (physical or virtual?) would be $50/month ?


#73

What does one CPU mean? How is it clocked? What’s its IPC? Basically, how many CPU instructions per second do I get?


#74

@andre1sk @sztosz Unfortunately cgroups, and therefore docker, and therefore Kubernetes, and therefore Gigalixir makes understanding CPU shares a little confusing. The gist of it is, if you have N containers on a Kubernetes node and they are given weights [w(0)…w(N)], then the proportion of CPU container i gets is w(i)/sum(w). On Gigalixir, the most common machine type we use has 4 CPUS and 16GB of memory. I’ve tried to set it up so that when you buy 1GB of memory, you get 1/4 CPU to max utilize the machine. In practice, the machine is never “full” so you’ll get more than 1/4 CPU. In fact, Kubernetes ensures that the machine is never more than 80% utilized.

Basically, you get a proportion of CPU relative to what else is on the machine, but it will never be less than 1/4 CPU when you buy 1GB.

See the CPU shares section here for more: https://engineering.squarespace.com/blog/2017/understanding-linux-container-scheduling


#75

@sztosz The details of what 1 CPU is can be confusing as well. Google Compute Engine describes it here: https://cloud.google.com/compute/docs/cpu-platforms

Basically, it is one hyperthread on one of the following, but you aren’t guaranteed a particular one because Gigalixir is run multi-zone.

  • 2.6 GHz Intel Xeon E5 (Sandy Bridge)
  • 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge)
  • 2.3 GHz Intel Xeon E5 v3 (Haswell)
  • 2.2 GHz Intel Xeon E5 v4 (Broadwell)
  • 2.0 GHz Intel Xeon (Skylake)

#76

So it’s basically something like n1-standard-16 instance divided into 16 chunks (if we are using 1GB increments) ?
so 1GB would be 1 hyperThread ?


#77

I think it’s actually a n1-standard-4 instance and I think it’s 1/4 of a hyperthread. GCE says, “For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), 2.2 GHz Intel Xeon E5 v4 (Broadwell), or 2.0 GHz Intel Skylake (Skylake).”

The n1-standard-4 machine has 4 virtual CPUs so 4 hyperthreads on the physical hardware. Divided in 16 chunks makes 1/4 a hyperthread per chunk.


#78

AWS is way too expensive, yet you people using google cloud infra should overprice your services.
I do not get it when you know dev ops so damn good, why not set up your data centers and break the Heroku prices.
this is the only way you would get extreme traction and rise up.


#79

It’s the peripheral tools that suck people in. Managed and monitored instances of various databases, redis, memcached, bigquery, Aurora, etc in the same datacenter.

I’d love to see Gigalixir on Digital Ocean personally though.