topspeed driver speed problem - poor performance

Hi,

I have made a simple test (with Clarion 5.5 patch G, using different  file
drivers) writing 500 values to database in a simple loop using just
ADD(value) to write to a file.

Interesting results with different drivers in winNT4.0:

1. topspeed driver - 7.2 seconds (in winNT4.0)
2. ODBC driver - 6 seconds (in winNT4.0)
3. basic driver - less than 0.02 seconds !!!!!!!!!!! (speed difference to
topspeed is close to 1:5000 !!!!!)
4. clarion driver - 1.2 seconds

Results in win2000:
1. topspeed - 65 seconds (yes, 10 times longer time than in NT!)

Does anyone know why the topspeed driver is this slow? As I see this, the
clarion topspeed driver has a major problem, performance is very poor (even
in NT4.0).

Also, it would be nice to hear from Clarion 6 users wheter the performance
is the same.

- Seppo Pyörret

On Fri, 12 Mar 2004 13:44:23 +0200, "Seppo Pyorret"
<seppo.pyorret@sr-instruments.com> wrote:
>I have made a simple test (with Clarion 5.5 patch G, using different  file
>drivers) writing 500 values to database in a simple loop using just
>ADD(value) to write to a file.

<snip>

>Does anyone know why the topspeed driver is this slow? As I see this, the
>clarion topspeed driver has a major problem, performance is very poor (even
>in NT4.0).

The TPS driver sacrifices speed for stability.  It is unbelievably
slow on all operating systems, but you only really notice when you are
doing mass updates or inserts.

Try your tests again, but this time LOGOUT the TPS file before you
start and COMMIT afterwards.  Should take somewhere around 1 second...

>Also, it would be nice to hear from Clarion 6 users wheter the performance
>is the same.

Same driver, same performance.  It ain't gonna change.

Jason

If you aren't sharing the files make sure you are not opening them shared
in the Global properties.

Also check out stream and flush.  I had an app with non shared files that
went so fast after these changes that when I blinked I missed my mass
update.

Bob

On Fri, 12 Mar 2004 09:08:52 -0600, Jason Berkan <jason_berkan@canada.com>
wrote:

> On Fri, 12 Mar 2004 13:44:23 +0200, "Seppo Pyorret"
> <seppo.pyorret@sr-instruments.com> wrote: 
>
> <snip>
> 
>
> The TPS driver sacrifices speed for stability.  It is unbelievably
> slow on all operating systems, but you only really notice when you are
> doing mass updates or inserts.
>
> Try your tests again, but this time LOGOUT the TPS file before you
> start and COMMIT afterwards.  Should take somewhere around 1 second...
> 
>
> Same driver, same performance.  It ain't gonna change.
>
> Jason