Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread EWB Server speed question
Thu, Feb 13 2014 7:39 AMPermanent Link

Uli Becker

I am loading this dataset using EWB Server:

select Parameter, Wert, Einheit, Default, AttentionPlus,
AttentionMinus from Laborwerte
where AnforderungenID = 78654
and Parameter <> 'kasse' and parameter <> 'privat'
order by Parameter

It needs about 400 msec to get the response.

When I define the dataset in EWB Server without the "order by parameter"
clause, it speeds up to about 30 msec.

There is an index defined for the field "Parameter", of course.

In EDB Manager I can't see a significant difference between both queries.

What can be the reason for that?

Thanks Uli
Thu, Feb 13 2014 8:58 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< In EDB Manager I can't see a significant difference between both queries.
>>

EDB Manager is not a good comparison - there you already have the
session/database open and there is some caching involved between multiple
executions.

More than likely, the reason for the difference is just down to the time it
takes to instantiate the dataset information for the call.  What happens if
you run the non-ORDER BY version first from a cold-started EWB Web Server ?

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Feb 14 2014 1:22 PMPermanent Link

Uli Becker

Tim,

> More than likely, the reason for the difference is just down to the time
> it takes to instantiate the dataset information for the call.  What
> happens if you run the non-ORDER BY version first from a cold-started
> EWB Web Server ?

EWB Web Server cold-started:
non-ORDER BY version:
1st execution: 360 ms
2nd execution: 50 ms

EWB Web Server cold-started:
ORDER BY version:
1st execution: 660 ms
2nd execution: 320 ms

rowcount = 16

Uli
Tue, Feb 18 2014 11:29 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< EWB Web Server cold-started:
non-ORDER BY version:
1st execution: 360 ms
2nd execution: 50 ms

EWB Web Server cold-started:
ORDER BY version:
1st execution: 660 ms
2nd execution: 320 ms >>

Are you running any AV software ?  The EWB Web Server is running the same
ElevateDB code as the EDB Manager, so the performance should be the same.
The only thing that I can think of that would account for the difference is
where the EWB Web Server is configured to write out temporary tables for
EDB.

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Feb 20 2014 4:01 AMPermanent Link

Uli Becker

Tim,

> Are you running any AV software ?  The EWB Web Server is running the
> same ElevateDB code as the EDB Manager, so the performance should be the
> same. The only thing that I can think of that would account for the
> difference is where the EWB Web Server is configured to write out
> temporary tables for EDB.

Locally (testing with localhost) yes: I am running NOD32. On the server
no. Results are the same.

Uli
Mon, Feb 24 2014 4:12 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< Locally (testing with localhost) yes: I am running NOD32. On the server
no. Results are the same. >>

I'm out of ideas, then.  If you want to pack up what you've got and send it
to me, I can take a look and see what's going on.

Tim Young
Elevate Software
www.elevatesoft.com
Image