Comments on: Enum Fields VS Varchar VS Int + Joined table: What is Faster?

By: Farrukh

Farrukh — Tue, 04 Aug 2009 18:54:38 +0000

In the test you used int+join table, what if we move the join table functionality to our application and just compare ENUM VS CHAR VS INT.

By: praca

praca — Sat, 28 Feb 2009 15:07:39 +0000

I use tinyint(1) to present value 0 or 1.
I thing enum, boolean and others methods works slower.

By: Little surprises « Arien’s Blog

Little surprises « Arien’s Blog — Sat, 21 Feb 2009 00:11:36 +0000

[...] about it, but after that session I was looking up some VARCHAR vs CHAR debate information and found this post on the MySQL Performance Blog. Turns out his idea isn’t really that crazy (performance-wise, at [...]

By: Получение списка возможных значений поля ENUM | Записки MySQL девелопера

Получение списка возможных значений поля ENUM | Записки MySQL девелопера — Tue, 20 Jan 2009 07:32:40 +0000

[...] Интересная статья о производительности полей типа [...]

By: somebody

somebody — Mon, 07 Jul 2008 15:59:14 +0000

have you guys tried indexing state_id on the cities_join table.
though I read something about frequent inserts with indexes being slow.
but would indexing speed things up?

and also

SELECT SQL_NO_CACHE c.city FROM states s LEFT JOIN cities_join c ON (s.id = c.state_id) WHERE s.name=’Minnesota’ LIMIT 10000,5;

since your searching by state maybe if you place it at the left mysql would search for that first and then search for the cities with similar state_id, and it will be ordered automatically.

ENUM is what got me to this blog, but since you guys said its dangerous, it’s no longer in my options.

By: Hakan

Hakan — Wed, 11 Jun 2008 14:26:46 +0000

Thanks for the test.

I think using the 4th way depends on the application. On our case, we store this kind of information in TINYINT and do the work in application, as we only select 25 of them at once. But when selecting thousands of row, and making change in all of them may not be better than storing in ENUM or varchar. I’ll do some tests about this when I have time and post here.

By: Raymond

Raymond — Thu, 08 May 2008 18:52:02 +0000

Thank you for these tests, it helped us find a solution to several issues before implementing.

By: confused

*confused* — Sun, 20 Apr 2008 07:18:30 +0000

16 bit fixed length integers vs random length strings (32 to 400 bits)

Shouldn’t the enum be several orders of magnitude faster, especially on sorts? I don’t understand.
Please explain to me why the benchmark shows only negligible differences.

By: Оптимизация работы с MySQL at Всякие интересные штучки для WEB-разработчика

Оптимизация работы с MySQL at Всякие интересные штучки для WEB-разработчика — Fri, 15 Feb 2008 02:11:46 +0000

[...] Хотя ENUM и противоречит нормальным формам, но, как показывают тесты, он быстрее других [...]

By: Оптимизация работы с MySQL | Записки маленького юниксоида

Оптимизация работы с MySQL | Записки маленького юниксоида — Thu, 14 Feb 2008 12:21:12 +0000