Database Design - Multiple Lookup/Enum Tables or One Large Table?

Question

I have many tables that use Lookup/Enum references for most of their column values. For example:
Person Table - PersonID | RaceCode | HairColorCode | HairStyleC

Answer 1

There's a potential performance difference.

A table with just 2 rows ties up a lot of space in cache for those two tiny rows.

If you have a lot of lookup values in a single table, you -- effectively -- pack those values more densely into cache.