Hi, Within the next year I was going to add another website to my account. Everything on my plan seems fine, except I was not sure what 'Site Memory Allocation 100MB' meant. Say I have a page which needs to load about 1MB of graphics and data. (A little html5 game.) Does this mean 100 people could load up the page at any one time. Or 100 people in an hour??? Once the page loads, will all the data be on the client's machine, so recalls to graphics wont be needed until they clear their internet? I am very confused about this. Hope you can help. Jon
100MB is the memory available in your application pool and it is not related to file sizes, downloads, etc. How your site will perform is dependent on how efficient your application is. It's impossible for us to say since you could have an application that serves 10,000 users every day without any problem, or one that exceeds the memory available in the application pool when one user hits it. It all boils down to how your application works.
From your response I am guessing the 100MB is a bit like RAM but on the server, rather than client machine. My present site is based around a Silverlight program. This downloads to the client machine (does a database check at startup) then makes no more calls to the server whatsoever (as Silverlight is a client based tech). So the overhead on the **Server** should just be the short database check. So I think I should be all right there. My new site will be based around an html5/js program. Again, I believe js is a client based tech, so when the page is running the javascript, that should all be done on the client machine and I am guessing should not affect the 100MB on the server. However, I do make a few database calls during the program which run php scripts. So this is my only server load area. These are reasonably light (significantly so compared to the js). Am I right in the way I am thinking? Is there any way I can test what RAM these small php-database-php scripts use up?
Yes, that's exactly what it is. Your application sounds relatively lightweight. You can test it by running it locally and watching the memory usage. But there's no easy way to simulate heavy use or traffic in your local dev environment. But generally speaking, if it's not using crazy amounts of memory locally, you probably won't have any problems running it live. If you do find that 100MB isn't enough memory for your application, our Max plan provides 200MB, and the ultimate plan 300MB. So you can "size up" so to speak.