hotsauce
Nov 25th, 2000, 12:49 PM
I am running a vb application on a NT network with five win95 clients. The application ties to an ms access database using ado. It has been running fine for 2-3 years, but now it has become slow at times. I have tried compacting and repairing the database. I have done some testing and this is what I found:
The system is a restaurant point of sale system. At the beginning of the day the system is very fast (in terms of accessing and updating data.) when it gets busy it is very slow (3-5 seconds to read or update a transaction.) Sometimes when it is not really busy, the system is still slow. I find this to be true when we have a lot of open checks or when it gets busy. When I say busy, it doesn't necessarily mean that 5 people are on the terminals at the same time. There may only be one person on the terminal, and it is still slow. At the end of the night when all the open checks are closed, the system is flies again. This problem just recently started happening. My hunch is that it is the server. It only has 64 megs of ram because it is old. My question to everyone is:
Does the server store the database in memory, and is the memory getting full during the business hours because it seams like if the system sits idle for a while, the system starts to fly again. I know I need to add more memory, but is it possible for the existing memory to go bad? Maybe it is the processor? That is old as well (PII 266.) Is the hard drive bad? What I'm trying to find out is how the architecture works when I request or update information from the server. Does the db sit in the server's memory or is it accessing strait into the server's hard drive???? Thanks everybody!!!
[Edited by hotsauce on 11-25-2000 at 02:09 PM]
The system is a restaurant point of sale system. At the beginning of the day the system is very fast (in terms of accessing and updating data.) when it gets busy it is very slow (3-5 seconds to read or update a transaction.) Sometimes when it is not really busy, the system is still slow. I find this to be true when we have a lot of open checks or when it gets busy. When I say busy, it doesn't necessarily mean that 5 people are on the terminals at the same time. There may only be one person on the terminal, and it is still slow. At the end of the night when all the open checks are closed, the system is flies again. This problem just recently started happening. My hunch is that it is the server. It only has 64 megs of ram because it is old. My question to everyone is:
Does the server store the database in memory, and is the memory getting full during the business hours because it seams like if the system sits idle for a while, the system starts to fly again. I know I need to add more memory, but is it possible for the existing memory to go bad? Maybe it is the processor? That is old as well (PII 266.) Is the hard drive bad? What I'm trying to find out is how the architecture works when I request or update information from the server. Does the db sit in the server's memory or is it accessing strait into the server's hard drive???? Thanks everybody!!!
[Edited by hotsauce on 11-25-2000 at 02:09 PM]