Hi MIke Nope, I'm looking for something a little more basic. What menu choice, object on the screen, etc do I click to see the number of page faults occuring?
David Blocker ----- Original Message ----- From: "Ramsour Mike" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 04, 2002 12:43 PM Subject: RE: Memory crashes in Windows 2000 > Dave: > > The idea is to watch this number for awhile. The info our IBM tech guy gave > me said something to the effect that if you start seeing page faults run > into the thousands (or possibly more) then that can indicate that you don't > have enough RAM installed. A page fault occurs when a program attempts to > get data from RAM but can't find it. It then has to read data from the disk > and/or swap file. The more RAM you have installed on your system the less > often the computer has to read from the disk and swap file. > > Hope this helps. > > Mike Ramsour > > -----Original Message----- > From: David M. Blocker [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 11:01 PM > To: [EMAIL PROTECTED] > Subject: Re: Memory crashes in Windows 2000 > > > > > > > Mike > > Thanks! > Its the same in Windows XP. OK, I've checked that off, now how do I keep > track of the crashes / page faults to see if I'm having the same low RAM > issue as you were? > > David Blocker > > > ----- Original Message ----- > From: "Ramsour Mike" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, October 03, 2002 8:05 AM > Subject: RE: Memory crashes in Windows 2000 > > > > David: > > > > In Windows 2000 do the following: > > > > 1. Right click on a blank area of the task bar > > 2. Click on Task Manager > > 3. Click on the Processes tab > > 4. Click on View > > 5. Click on Select Columns... > > > > This brings up a dialog box that allows you to select a wide variety of > > measurements to track. > > > > Hope this helps. > > > > Mike Ramsour > > > > -----Original Message----- > > From: David M. Blocker [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 03, 2002 8:45 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Memory crashes in Windows 2000 > > > > > > > > > > > > > > Mike > > > > "Incidentally, I also configured the Windows Task Manager to keep track of > > page faults." > > > > Can you clarify how to do this? It sounds very useful (I'm running Windows > > XP and also have regular crashes out of programs that I'm dealing with) > > > > David Blocker > > > > ----- Original Message ----- > > From: "Ramsour Mike" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, October 03, 2002 7:15 AM > > Subject: Memory crashes in Windows 2000 > > > > > > > Good morning: > > > > > > I have posted recently about memory crashes that I was encountering > > running > > > R:Base 6.5++ on a Windows 2000 system. In the hopes that this may help > > > others I am happy to report that (at least tentatively) I have found out > > > what the problem was. > > > > > > It appears that the way my system was configured and the amount of disk > > > space I had available was causing the Windows swap file to run out of > > space. > > > Coupled with this was that when I reloaded my database I ran low on disk > > > > space. Put these two together and I was crashing about every day during > > my > > > morning program run. I have moved the swap file to my D: drive which > has > > > more space and also archived several hundred megabytes of database. > Since > > I > > > have done this I have not had a problem all week. > > > > > > This may explain why I was having similar problems when running > Microsoft > > > Excel. It would have occasional memory crashes when working with large > > > files. > > > > > > Incidentally, I also configured the Windows Task Manager to keep track > of > > > page faults. Having a high number of page faults can indicate that you > do > > > not have enough RAM installed on your system. A page fault happens when > > the > > > requested data/memory is not in RAM and has to be retrieved from the > disk > > or > > > swap file. In my particular case, my system had nearly 700,000 page > > faults > > > in the spooler program alone during a 12 hour period. I am having the > RAM > > > on my system boosted from 256 MB to 768 MB as soon as possible. My new > > > system, which I'm supposed to get in a week or two is coming configured > > with > > > 1GB of RAM and a 2.0 gHz Pentium IV. Woo Hoo!!! > > > > > > Hope this helps someone out there. > > > > > > Thanks > > > > > > Mike Ramsour > > > Voice: 1-740-829-4340 > > > ================================================ > > > TO SEE MESSAGE POSTING GUIDELINES: > > > Send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: INTRO rbase-l > > > ================================================ > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > ================================================ > > > TO SEARCH ARCHIVES: > > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > > > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
