I'm trying to eliminate causes for a great slowdown I'm experiencing.  I
upgraded a location from v3 C/S to v4 C/S and I'm getting all sorts of
complaints about speed.
Before I hit their hardware, I just wanted to make sure there's no reason
for v4 to be greatly slower than v3.  I'm running v4.24b1 and it was
compiled using the DBISAM MM (default).  All the users access the data via
C/S and I have a processing program that resides on the same machine and
access the data directly.  Is v4 C/S more chatty?  Well, whatever is going
on, the hard drive is peaking under any moderate load.  With v3, they were
doing just fine (so it seems).  Even if the C/S stuff ended up slower, the
direct access stuff is taking much longer.  For example, a process that used
to take about 10 minutes is taking about 3 hours with no change to the code.
Any ideas?

Thanks,
Bill

Interesting....not my experience at all under the same scenario.

B Miller wrote:
> I'm trying to eliminate causes for a great slowdown I'm experiencing.  I
> upgraded a location from v3 C/S to v4 C/S and I'm getting all sorts of
> complaints about speed.

> Interesting....not my experience at all under the same scenario.
I wouldn't thinks so.  I'm going to be testing their drives later today to
see if that is the problem.  They've had drive problems in the past so maybe
it is still their problem.

Bill

Bill,

<< For example, a process that used to take about 10 minutes is taking about
3 hours with no change to the code. Any ideas? >>

Wow, that's pretty bad.  And no, you shouldn't be seeing anything like that
with 4.x, so the issue is most likely environmental.  Is there any AV
software installed on the same machine ?  That would be the first place I
would look for slowdown issues.

--
Tim Young
Elevate Software
www.elevatesoft.com

If that 10 min procedure has anything to do with running large Insert
SQL statements. I found that running those from the client was slower
in v4. Tim got me onto v4's server side procedures and that fixed my
speed problems.

Ivan



--

Ivan,

<< If that 10 min procedure has anything to do with running large Insert SQL
statements. I found that running those from the client was slower
in v4. Tim got me onto v4's server side procedures and that fixed my speed
problems. >>

Good point.  V4 sends scripts a statement-at-a-time to the server whereas
3.x sent the whole thing at once.  This was done in V4 to allow for scripts
to be parameterized.  The solution in V4 is, as you say to convert large
scripts into server-side procedures.

--
Tim Young
Elevate Software
www.elevatesoft.com