Scaling to 100M: MySQL Is a Better NoSQL

Re:Scaling to 100M: MySQL Is a Better NoSQL by narfz on Tuesday May 24, 2016 @04:29PM (#11765213)

we did the same and then switched to the native UUID type. it eliminates the need for a unique index and we saw a drop in storage space by 1/2. it's totally worth converting UUID to the uuid field.

ALTER TABLE my_table ALTER COLUMN my_uuid TYPE uuid USING uuid::uuid;

[ Parent | on HN ]

Re:Scaling to 100M: MySQL Is a Better NoSQL by olavgg on Tuesday May 24, 2016 @05:12PM (#11765532)

And you want as much of the index as possible in RAM. When the index is 10 times larger than necessary and do not fit in your RAM, you get a very expensive performance penalty!

[ Parent | on HN ]

Re:Scaling to 100M: MySQL Is a Better NoSQL by StevePerkins on Wednesday May 25, 2016 @07:59AM (#11769104)

Same, but we use raw binary columns (i.e. "BINARY(16)" for MySQL and "BYTEA(16)" for PostgreSQL).

Conversion between the database-native UUID type and the application-layer UUID type is often so flaky (particularly with Java and JPA).

[ Parent | on HN ]