I'm making a site and will have a table that will store a user's contact info, display preferences, and more. In normal form they should all be on the same table, but I anticipate that eventually I might have a hundred rows on each profile table. Aside from being less human readable, will it be any slower? Would it be better to use separate tables with foreign keys referencing a main profile table for different categories of information? If there's less rows, won't SQL use less memory when performing table joins?