Good morning: I have experienced a major change in the performance of the RELOAD command with the last two in-line patches for R:Base 6.5++. I am running under Windows 2000 SP-3 with 1 GB of RAM on a 2 GHZ Gateway e-series system. I have 20+ GB of available disk space. Back in October when I first got my system, reloads were taking about 10 minutes. Now they're taking up to 45 minutes. I have actually trimmed my database size down to under 1 GB from 1.4 GB during that time so there's less data to work with. It's the data reloading part that is taking the longest. Reindexing goes by in a flash.
Doing a full UNLOAD ALL and running the resulting file takes about 10 minutes. Any ideas on what might be going on? Why is the RELOAD taking so much longer? The frustrating part besides this is that sometimes RELOAD goes very quickly. I watched the CPU usage in Task Manager during the RELOAD and a lot of the time the CPU was only being used from 0% to 4%. No other applications were running at the time. I run about 40 programs each morning. I recently redesigned my technique using the QUIT TO syntax. It was my understanding that this uses memory more efficiently or will release memory when the QUIT TO is executed. I watched the Performance tab in the Task Manager as it steadily increased from an initial value of 5,546 K when R:Base started up to 64,268 K as the programs progressed. Is this normal? Is R:Base releasing memory correctly? Is there a better way to run programs? I have experienced frequent Windows 2000 memory crashes running R:Base lately. There was some indication that there might be a problem with the interaction between Norton Antivirus and the Acrobat Distiller software that I used to create PDF files from R:Base reports. My programs often crash right at the point where printing begins. I have tried tweaking the system and making sure I have the latest versions and patches but I am still getting the crashes. Again, I did not have these problems back in October. There have been R:Base updates and Windows 2000 critical updates since then. How can I tell what has changed? I have scrubbed my code "raw" looking for possible errors. I found one hanging continuation character in one program but by and large every was pretty much squeaky clean. Desperately seeking answers and stability. Mike Ramsour 740-829-4340
