This is a direct follower to this question. An answer given to that questions says (my understanding), that nowadays using string-based enums instead of integers isn't a much problem, because hosting costs and general DB costs are today much, much lower, so we can afford for some "database size waste" (generalization).
I'm interested, at which point this can turn itself around and even in nowadays become a real problem?
Suppose I have a table with n columns, out of which four columns uses string-based enums instead of integers. Assume, that each enum is 8 characters long, if that matters (probably yes -- string column size). Now, suppose, that I'm filling this table with records. When I may start thinking, that using enums was a wrong decision?
At 100k records? At 1M records or maybe not before reaching 1G of records?
Is there an easy way for me to determine:
what would be size difference, if my database with n records would be using integers instead of strings?
what general database size could become a real problem for my hosting?
I've heard that on simple, shared hosting a 1 GB database size becomes a problem and bigger databases are not allowed / not much liked by hosting's admins. But, since I'm a complete database newbie, I don't know, if that is true? And how does it becomes, when we talk about VPSs or even dedicated hosting?