I have a weird recurring problem that I don't think anyone could give a direct answer too, but I will put it out there in case anyone could possibly shed some light on it.

I am still using 4.25 (upgrade planned soon to latest) but everything generally works fine.  I have one table in particular that gets used either directly or as part of a join on a client/server basis with approx. 30 users a day.  I am finding that when the server starts up, the table use with 30 people connected is fine, this gradually gets worse over a time period, could be a day, could be a whole month or more before any issues are noticed.  I am finding that on a good day it could take 0.5 seconds to run a simple query, no joins on the table, on a bad day this can be between 5 - 7 seconds.  Once the table has slowed down, it stays that way, even when everyone has disconnected, the only way to improve it is to restart the server and everything goes back to being great again.

Does anyone have any idea of what could cause such a scenario?

Cheers.
David.

David,

<<the only way to improve it is to restart the server and everything goes back to being great again>>

Do you mean restart the computer or only the DBISAM server?
Have you tried to monitor the allocated memory on the server over time?

--
Fernando Dias
[Team Elevate]

Hi Fernando.

I mean a restart of the DBISam Server only.  Yes I have watched the memory and its seems to be about right, so nothing of concern there I think.

Fernando Dias wrote:

David,

<<the only way to improve it is to restart the server and everything goes back to being great again>>

Do you mean restart the computer or only the DBISAM server?
Have you tried to monitor the allocated memory on the server over time?

--
Fernando Dias
[Team Elevate]

David


I used to see the same effect with a  fileserver app, My eventual conclusion was a) I couldn't cure it and b) it was something to do with network buffers (Windows' not DBISAM's)

I can 100% guarantee the accuracy of a) - not sure about b)

I haven't seen it happen with ElevateDB

Roy Lambert

David,

I would say that your best bet at the moment, and as you were already thinking of upgrading, would be to upgrade to the latest version and then see what happens then.

--
Fernando Dias
[Team Elevate]

Hi Roy.

Yes I think a) is where I am at, at the moment.  I can live with it, but could live without it

Just thought I would put it out there to see if anyone had same issue and worked around it.

Cheers
David.

Roy Lambert wrote:

David


I used to see the same effect with a  fileserver app, My eventual conclusion was a) I couldn't cure it and b) it was something to do with network buffers (Windows' not DBISAM's)

I can 100% guarantee the accuracy of a) - not sure about b)

I haven't seen it happen with ElevateDB

Roy Lambert

Fernando.

Yep that is exactly what I intend to do, just need people to stop maxing out the company credit card first!

I will probably get this done next month, off on holiday in 2 weeks and don't want anything going wrong while I am away.

Thanks anyway.
David.

Fernando Dias wrote:

David,

I would say that your best bet at the moment, and as you were already thinking of upgrading, would be to upgrade to the latest version and then see what happens then.

--
Fernando Dias
[Team Elevate]