Runtime performance on SH3 Processor

[Guest]

Hey gang.

I need a little expertise. We have a handheld application that uses SQL CE
and Replication etc. The app takes 55 seconds to do a very simple SELECT
query on an app we wrote using VB.NET and SQL CE. The table it is searching
has 31,000 records though.

When we run the app on a quite old IPAQ it takes approx 5 seconds.

The hardware vendor of the handheld using the SH3 says we should optimize
our code. I don't see what we can optimize.

Here's the question I have though.
Is the JIT MS build for the SH3 optimized or is it just an interpreter or
not very optimized because SH3 is not very popular as Intel ARM etc?

Is an SH3 processor just bad at performance in general? This SH3 processor
is 180 mhz. It has 64mb of ram and 64mb of flash (where we are storing the
24mb DB file).

Could anyone comment please?

Also, I have noticed Visual Studio 2005 (.NET 2.0?) has updates to SQL CE.
Is this a new version that is perhaps much quicker?

I guess my bottom line is. Is the processor just damn slow or what? lol.

I appreciate any comments.

Thanks and take care.

 

[Chris Tacke, MVP]

The CF 2.0 ARM binaries are optimized, but I doubt it would account for
differences that large. All other aspects are equal (DB location, indexes,
etc)? Even 5 seconds for a query seems pretty slow if the filter's field is
indexed.

-Chris

 

[Guest]

Thank you so much for the reply Chris.

We did some further benchmarking after I posted my question here and this is
what we did:

1. Execute the query in Query Analyzer CE (to eliminate our code, and see
how long the raw query takes to execute): 46 seconds to return 721 records
2. Write a 2 control winform test case which simply inserts 721 records into
a ListView to benchmark how long it takes: 16 seconds.

Combined: 62 seconds

These two things eliminate our actual VB.NET code all together. When we
execute the whole thing in our app it takes 67 seconds. So where are the
extra 5 seconds? Doesn't matter, between data marshalling for .NET I imagine
it would eat up some time on 721 records multiplied by 4 columns for the
fields we query for.

But I think this basically proves, if it takes 46 seconds for QA to even
execute the query, and a whopping 16 seconds just to insert records into
ListView. That means the processor is damn slow correct?

I believe the fields are indexed before we replicated to the handheld. Or do
we have to do further indexing actually on the handheld somehow?

Thanks so much for everything!