MySQL BIGINT v INT. Is there a big deal? →

Even with these simple tables and small data sets it’s clear that INT is a saving of disk space over BIGINT. In many clients I’ve seen huge savings in multi TB databases, just with a small number of schema optimizations. If this saving alone for a more optimized database design was only 10%, it is an easy 10% that will reflect a direct improvement in performance.