I'm sure your app is using nowhere near that. (God save us from hosting providers who think that you can put a definite number on memory usage under an OS that handles virtual memory, lazy allocation, and shared memory well, as Unixes do; I'm going to assume the OS is Linux for the purpose of this post just because I'm most familiar with it.)
I just spot checked my current app and it was "using" 159MB of virtual memory. This is what most people look at, which is sad because it is a nearly meaningless number. It is the amount of memory that your app has said that is *might* use. More useful is the resident set. (Sometimes labeled RES or RSS.) That same app has a resident set of only 15MB. Apps almost never use anywhere near all the memory that they say they might. (This could actually be a problem if your provider has disabled memory overcommit, but otherwise, not really.) In addition, this app shows that about 3MB is shared with other apps. I have almost nothing in the swap on this machine, so I can say that if I killed this app, I'd be freeing up about 15mb - 3mb = 12mb of memory. And that sounds a lot less "impressive" than the 159mb that it is "using". The command that you provide shows the virtual memory. I should say that it is my understanding that Windows does not do shared memory very efficiently, but I'm sure it still does lazy allocation, which is most significant in my example app's case, and probably yours too. (I should also say that I am pretty unfamiliar with Windows' VM.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
