Hi,

I have a couple of customers using DBISAM C/S v3.3 that have reported a slow
down in the system during the day.  In some cases the slow down appears to
be as little as a couple of seconds.....in some cases it appears to be alot
longer.

Unfortunately I have not got any benchmark information to justify these
claims :/

I am just interested to find out if other people have a similar
problem.....is it a DBISAM/windows thing....is there anything that I can do
to either find out what is going on....or to improve things.

The users only have about 8-12 users concurrently on the system.

Regards
Trevor Keegan

"Trevor Keegan" <tkeegan@ealink.com> wrote in message
news:03F7619D-3751-4252-A21D-6AAD1300A84F@news.elevatesoft.com...
> Hi,
>
> I have a couple of customers using DBISAM C/S v3.3 that have reported a
> slow down in the system during the day.  In some cases the slow down
> appears to be as little as a couple of seconds.....in some cases it
> appears to be alot longer.
>

That depends on what they are doing, for instance is it a booking system?
sales system ? or updating records.
In my former booking system under V3   10 people max inputing data for
a busy taxi company it was as fast as lightning (just a new append) get 3
or 4 query's from customers to change times and so on not a problem.
As soon as accounts clerks get near a computer they open in edit and go
of making coffee and yakking leaving everything locked up.
I implemented a snapshot field datetime and copy the record to temp table
for an edit on repost if the snapshot datetime dont match it doesnt post.
It always posts tho.

> Unfortunately I have not got any benchmark information to justify these
> claims :/
>

Customers are never right, but figure out if its the coffee break effect 1st
dont let them know tho. Re-think your editing if more than one has it open
someone else making coffee some dumb man talking football it will slow
dont lock the tables until you press post...

> I am just interested to find out if other people have a similar
> problem.....is it a DBISAM/windows thing....is there anything that I can
> do to either find out what is going on....or to improve things.
>
Yes we all have had that problem
No its not a DBISAM/Windows thing its human input clerks...
Improve how you manage file editing.
Someone in here posted about file locking once cant find it now
but it was well covered.
Desktop is easy but CS is a whole new ball game.

> The users only have about 8-12 users concurrently on the system.
>

2-3 clerks can lock it up 1st port of call the head honcho may
think he is checking up on his staff probaly screwing it up.

Oh! is this lan or wan coz wan slows down daytime hours should
have been my 1st thought.
Rita

Hello Rita,

Thanks for the reply.....I am talking about a LAN environment here.

I have FlushBuffers property set on the Session as well....if this may make
a difference.  The system that I have is a Tax Compliance system that is
used by Tax Agents.  During the Peak period it will probably see Tax
Information for about 2000 clients being pushed into the system within a
period of 1 month.

They have reported that aside from the slow-down, some PC's are occasionally
locking up, but I have not been able to establish whether it is isolated
machines that are locking up or not (you know how users are :-/ ).  I have
alread included the GetServerDateTime in a timer every 10 secs to keep the
session alive.....but the timing may be something that I might have to
review...what sort of frequency have used used in your systems?

So then we come back to the mysterious issue of the system/network/etc
slowing down.....I have also told them that speed is a very subjective
thing....and that even though you might like to think that multi-tasking
means running processes simultaneously....it does not always work that way,
so there will always be times when information needs to be queued.  So I am
just exploring here to find out if this type of phenomena is 'real'

Regards
Trevor Keegan

Trevor,

<< I have a couple of customers using DBISAM C/S v3.3 that have reported a
slow down in the system during the day.  In some cases the slow down appears
to be as little as a couple of seconds.....in some cases it appears to be
alot longer. >>

Check the Windows server's event log and make sure that nothing weird is
getting started up like a system backup, etc.   More than likely this is
external, but I would also check to make sure that you don't have any
queries or filters executing that have to perform a brute-force scan of a
very large table.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for that....I will check it out....there are apparently one or two
areas in the system that people seem to notice abit more than others.....so
I will have a look at the queries there.

Given that I only have 2 sites at the moment that I am trialing the C/S
implementation in, and both give completely different accounts of
performance....but both have roughly the same amount of data.....I would say
that there most likely is something envionmental going on...but I wanted to
check that there isn't any other possibility.   BTW, is there a general rule
of thumb to follow in terms of the best frequency to contact the server to
refresh the session?

Regards
Trevor Keegan

Trevor,

<< BTW, is there a general rule of thumb to follow in terms of the best
frequency to contact the server to refresh the session? >>

With 4.x, we use a default ping interval of 60 seconds.   It simply has to
be slightly lower than the session timeout setting on the database server in
order to avoid having the database server disconnect the session, and
possibly remove it if the dead session expiration time setting is
particularly low.

--
Tim Young
Elevate Software
www.elevatesoft.com