Mariette, I wouldn't count on that.

It will crash less, because it will use lesser memory. But chances are high DNN will spike over 100MB again sometime in the future. BTW if you cache to disk, your hoster will complain about excessive IO usage of your application. To stay below 100MB you would also need to disable the scheduler, no search, no users online, no logs. You should also never again log in as host, and do alot of portal administration in a short time.

100MB is just not enough, DNN needs to be able to go over that value, it won't stay that high, dnn will release it's memory, but sometimes memory usages will be higher than 100MB

***you could tell your hoster, that if they put all DNN instances in the same app pool they will conserver memory (by not having to load .NET framework multiple times). You also need to tell your hoster to remove that memory limit. OR you could find a better hoster

yes, going dedicated is definatly the only solution for any serious online project. The bad part is that rackspace only starts to be affordable once you need at least 10 MBit (at least here in europe)

For smaller projects the best solution is renting a portal with a *real* dnn hoster. I really mean renting a portal, not webspace. Remember that DNN is designed for this use case.

You definatly DO NOT want to slap DNN on a 3$ / month hosting plan.