Session duration will greatly influence concurrent usage. If people use your service for less than five minutes per day then 100 daily users would mostly have the system to themselves. This means that you could have thousands of registered users and grossly inefficient code without load issues.
Stop fretting about your hardware and get thousands of registered users.
Thanks. I expect my sessions to be longer (30 minutes?). And if I were only expecting hundreds of users, I wouldn't waste my time. I'm hoping to hit at least tens of thousands of registered paying users. I do expect to have portions of "grossly inefficient code" (much faster to implement in some cases) initially that I plan on solving (when they become the problem to solve). My product/site will be highly collaborative (I know, everyone thinks this, but, I think my idea is different (I know, everyone thinks... ())) and with a larger than normal communication component.
Session duration will greatly influence concurrent usage. If people use your service for less than five minutes per day then 100 daily users would mostly have the system to themselves. This means that you could have thousands of registered users and grossly inefficient code without load issues.
Stop fretting about your hardware and get thousands of registered users.