I think you need to be careful and not draw too many conclusions from the percent of memory used. With the newer OSs (Vista and 7), the OS uses as much memory as it can to improve through put. It analyses the applications that you run on the PC (real time) and caches as much of the application as possible to memory to speed up execution. If you are running the same program over and over (such as RBase), it will cache more and more of the application causing memory usage to grow (that is a good thing). I am not sure, but I believe that Server 2008 operates that way when you are running TS.
John From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, February 17, 2010 9:29 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Memory Usage out of hand Rachael, Could you please post : A) What process in the task manager you are seeing "consume" memory and not releasing it. I.E. RBG8.exe or compiled.exe etc. B)Do you see this memory consumption on work stations as well as terminal server? On terminal server, you would see either a RBG8.exe or a compiled.exe process for every user running the program. Does all user's process's climb at about the same rate or do some consume more than others. I am interested in this as I use terminal services to a great extent. I have not had problems in this area, although on occasion, I do have terminal services seem to lock up on Rbase sessions. I have never really monitored the memory before, but am doing so now as we speak. I have about 20 sessions running on TS. All compiled exe's are showing between 12,000K and 22,000K of memory usage. However, after several minutes, I have not seen them grow any. One exe however, is using 69,000K. This app does not use any "outside" controls other than it does use a form timer extensively. This may be an external Windows function. However, while it is using 3X more memory, I do not see it growing at this time. I will monitor it over time via PerfMon. Let me know what exe's you are comparing and what machines. Thanks, -Bob ----- Original Message ----- From: "Rachael Malberg" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, February 17, 2010 7:27:18 AM GMT -06:00 US/Canada Central Subject: [RBASE-L] - Re: Memory Usage out of hand I am curious if the browser control is the issue, would closing the form with control free up memory? So perhaps the code rather then refresh the form, would close and re open the form? and just to clarify Larry, using your example you are right but my emphasis was a shared app on a windows network (this is very apparent with more then one user connected and at least one user is entering data) the memory usage will continue to rise as you work and not drop much no matter what you do. If anyone is interested you can get the same results using RRBYW14. Now granted, maxing out RAM has not been an issue however I have multiple users RDP into a server to use an app all day long, once they start hitting 150,000+ k by the afternoon, they MAY experience what we call 'weirdness' which means, temp data doesn't get loaded or updated, forms/reports don't load completely, or the I/O and lock up issues. They will sign out, sign in and return to what they were doing and it will work fine. I would love any suggestions on how to clear allocated memory because clearing variables, disconnecting/reconnecting, and deleting scratch files doesn't do it and honestly I don't know if it is possible since I think this is a MS file sharing thing. ----- Original Message ----- From: "Lawrence Lustig" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, February 16, 2010 1:29 PM Subject: [RBASE-L] - Re: Memory Usage out of hand > << > As it's used, memory use will grow all day long, and no matter what is > done, it will not clear till the app is closed. You (and infact everyone) > should see this behavior with other shared apps on a windows network, > although you won't reach a 'tapped out' state for most, you will see the > memory use will grow and grow as people use it but it will never go down > no matter what >>> > > This is not correct. A well-written program will allocate and deallocate > memory as needed, and you will see its memory usage go up and down as you > use it. > > To see this happening in R:Base, start R:Base and open the task manager. > Look at the memory R:Base is using. Now, RBEDIT a really large text file > (multiple megabytes). You'll see R:Base's memory usage shoot up as it > loads and processes the file. When the file is fully loaded, R:Base will > release some of the memory it used during the load process, but will still > be using a good deal more memory than it was originally (naturally, > because it has that large file open). Now, close RBEDIT and you'll see > R:Base's program usage drop back to approximately what it was when you > started it. > > R:Base is allocating and deallocating memory as needed. > > Unfortunately, many programs do leak small amounts of memory so that, as > their memory usage goes up and down during the course of a session, it's > on a somewhat upwards trajectory. When that happens in a process linked > to your application (in this case, perhaps, the Internet Explorer browser > control) then your application will appear to be the one using the memory > and there isn't much you can do about it. > -- > Larry > >
