I converted a DBISAM3/ASTA program to use EDB 2 C/S. One customer is
saying the new version is much slower than the old version for the
remote client. They use a T1 to access the main site. Queries are
pretty well index optimized and sensitive. Anything else I might not
have thought of? I don't use RemoteCompression. Would that help much?

Michael,

<< I converted a DBISAM3/ASTA program to use EDB 2 C/S. One customer is
saying the new version is much slower than the old version for the
remote client. They use a T1 to access the main site. Queries are pretty
well index optimized and sensitive. Anything else I might not have thought
of? I don't use RemoteCompression. Would that help much? >>

Yes, that will help immensely over any type of connection that has less than
10Mb of bandwidth.  Did they happen to indicate what portions of the
application are slow ?  The biggest slowdowns in Delphi applications over
WANs are due to chattiness and latency, so you need to avoid things like
lookup fields and calculated fields that cause further data access.

Using cached updates helps in situations where you want to bring over a set
of rows, edit them, and then send back the edits, such as in a master-detail
situation.

--
Tim Young
Elevate Software
www.elevatesoft.com

On Mon, 7 Jun 2010 17:10:30 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< I converted a DBISAM3/ASTA program to use EDB 2 C/S. One customer is
>saying the new version is much slower than the old version for the
>remote client. They use a T1 to access the main site. Queries are pretty
>well index optimized and sensitive. Anything else I might not have thought
>of? I don't use RemoteCompression. Would that help much? >>
>
>Yes, that will help immensely over any type of connection that has less than
>10Mb of bandwidth.  Did they happen to indicate what portions of the
>application are slow ?  The biggest slowdowns in Delphi applications over
>WANs are due to chattiness and latency, so you need to avoid things like
>lookup fields and calculated fields that cause further data access.
>
>Using cached updates helps in situations where you want to bring over a set
>of rows, edit them, and then send back the edits, such as in a master-detail
>situation.

The customer claimed adjusting the compression level is of no help.
What do you mean by lookup fields and calculated fields? Like a
TDBLookupCombobox? I use many of those on one form but that is not the
form they are complaining of. The app doesn't use any master-detail
implementations.

Michael,

<< The customer claimed adjusting the compression level is of no help. What
do you mean by lookup fields and calculated fields? Like a
TDBLookupCombobox? I use many of those on one form but that is not the form
they are complaining of. The app doesn't use any master-detail
implementations. >>

Can you email me the code/form that they're complaining about ?  That will
help immensely, since I can tell you exactly what to optimize.

--
Tim Young
Elevate Software
www.elevatesoft.com

Michael


Probably nothing to do with it but since file extensions have changes is there an AV that was ignoring .dat etc and isn't ignoring the new extensions?

Roy Lambert

On Wed, 23 Jun 2010 18:35:33 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< The customer claimed adjusting the compression level is of no help. What
>do you mean by lookup fields and calculated fields? Like a
>TDBLookupCombobox? I use many of those on one form but that is not the form
>they are complaining of. The app doesn't use any master-detail
>implementations. >>
>
>Can you email me the code/form that they're complaining about ?  That will
>help immensely, since I can tell you exactly what to optimize.

Just heard back from the customer today. They said the compression
actually does help but they had to reboot the server. Also they have
to reboot the server every day or it slows down again. Why would that
be?

Michael


It sounds as though you have a similar situation to myself. The main difference is that I'm using file server mode on my small network: 2 Vista, 1 XP client and 1 XP as server.

My app runs fine most of the time, but on occasions moving between records is a bit molasses like. Sometimes reboot the client fixes it, sometimes reboot the server does and sometimes it takes shut down everything.

I've tried various things without a cure and I'm beginning to wonder if its my 6 year old Netgear router just getting tiered. I may try giving it a holiday soon.

Roy Lambert

Michael,

<< Just heard back from the customer today. They said the compression
actually does help but they had to reboot the server. Also they have to
reboot the server every day or it slows down again. Why would that be? >>

Reboot the entire server machine ?  I have no idea.  Did someone actually
analyse the machine to see what the status of the memory, CPU, disk, etc.
was ?

--
Tim Young
Elevate Software
www.elevatesoft.com