Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#1

Post by Zenfinch » Fri, Sep 02, 2016, 7:38 PM UTC

Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness
aws.amazon.com

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#2

Post by ralusek » Fri, Sep 02, 2016, 10:16 PM UTC

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore.

I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#3

Post by Scarbutt » Fri, Sep 02, 2016, 10:26 PM UTC

ralusek wrote: post #2

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore. I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

I can't live without the occasional JSONB anymore.

Some can't live without Aurora anymore ;) - they start their projects with MySQL(even thought they prefer Postgresql) to be Aurora compatible, just in case they need it.

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#4

Post by n00b101 » Fri, Sep 02, 2016, 10:59 PM UTC

Does this support column-oriented database designs?

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#5

Post by s0l1dsnak3123 » Fri, Sep 02, 2016, 11:43 PM UTC

ralusek wrote: post #2

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore. I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

I second this. I'd switch over from RDS to Aurora in a heartbeat if AWS built a postgres frontend for it.

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#6

Post by kondro » Fri, Sep 02, 2016, 11:43 PM UTC

ralusek wrote: post #2

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore. I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

Laaaaazy. :P

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#7

Post by pinouchon » Fri, Sep 02, 2016, 11:45 PM UTC

Scarbutt wrote: post #3

ralusek wrote: post #2

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore. I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

I can't live without the occasional JSONB anymore. Some can't live without Aurora anymore ;) - they start their projects with MySQL(even thought they prefer Postgresql) to be Aurora compatible, just in case they need it.

I'm curious what are the reasons some people "can't live without Aurora anymore". I would love to hear specific benefits of Aurora, regarding performance or other aspects.

The comparisons I could find didn't seem to be very favorable to Aurora (mainly that the claimed 5x improvement does not show up in the benchmarks)

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#8

Post by brianwawok » Fri, Sep 02, 2016, 11:56 PM UTC

n00b101 wrote: post #4

Does this support column-oriented database designs?

It's still MySQL

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#9

Post by brightball » Sat, Sep 03, 2016, 1:14 AM UTC

pinouchon wrote: post #7

Scarbutt wrote: post #3

Earlier quoted context omitted.

I can't live without the occasional JSONB anymore. Some can't live without Aurora anymore ;) - they start their projects with MySQL(even thought they prefer Postgresql) to be Aurora compatible, just in case they need it.

I'm curious what are the reasons some people "can't live without Aurora anymore". I would love to hear specific benefits of Aurora, regarding performance or other aspects. The comparisons I could find didn't seem to be very favorable to Aurora (mainly that the claimed 5x improvement does not show up in the benchmarks)

I moved a 60GB database too it last year that we had setup multi AZ.

We cut our costs by about 40% after the switch and saw about a 20% boost in speed. RAM usage was lower too.

One of the biggest savings is that you don't need multiAZ since your data is stored redundantly. You don't have to worry about failover because the restart time is The man hours alone that we used to put into actively watching and tuning that DB have just vanished as has almost the entire sysadmin burden. That project was already on MySQL too which made it an easy move too.

I wish they'd do something similar for PG too.

Re: Amazon Aurora: Parallel Read Ahead, Faster Indexing, NUMA Awareness

#10

Post by craigkerstiens » Sat, Sep 03, 2016, 1:14 AM UTC

s0l1dsnak3123 wrote: post #5

ralusek wrote: post #2

Cool, although I sure wish they had gone with Postgres. I can't live without the occasional JSONB anymore. I know MySQL has made some half-hearted attempts to make headway on this front, but it has completely changed the way I model certain parts of my data.

I second this. I'd switch over from RDS to Aurora in a heartbeat if AWS built a postgres frontend for it.

Curious what is the key feature of Aurora on Postgres that you'd want?