Interpreting Performance Statistics

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In my continuing effort to determine why my app occasionally and randomly
"hangs", I have turned my focus to performance statistics. I have read
descriptions about what the performance stats are, but I havent come across
anything that states "benchmarks" for me to determine which of my stats are
abnormal.

My app is a data collection application and here are a few of the stats from
a simulation of the entry of 450 records (typical of avg day).

Number of Objects Allocated = 248476
Number of Simple Collections = 0
Number of Compact Collections = 73
Number of Full Collections = 3
Number of Calls = 21678872


Do any of these stats look abnormal to anyone? Are there other stats that I
should be paying particular attention to? I'm wondering if the application
could "hang" if the user is trying to do something during a collection
(particularly a full collection)?

Thanks!

Mike
 
Hi Mike!!!!

Are you inserting rows in a local database in, say, SQLCE??? If so, I
strongly recommend to verify if you have enough memory to both save the
information in your pocket PC AND to run your application. To check this, go
to the "Memory" applet in your control panel exactly the moment that you're
collecting information.

In many cases, the memory of the device is divided in halfs between
storage and execution by default. If you ran out of ram for either execution
or storage, Windows Pocket PC will try to re-arrange its memory
assignation... but it does take a while. This may have an impact for every
insert statement you execute.

Hope it helps!!!

Tarh ik
PS: This posting has been posted "AS IS"
 
Thanks Tarh-

Perhaps I should of clarified that the app goes into a "dead lock", not just
a temporary hang. It requires a soft reset of the device.

To answer your question, yes I am inserting data into a pocket access table
and am currently testing to see if perhaps it is a memory issue. Do you
think that having the Pocket PC reallocate memory as I am entering data could
cause a dead lock? I never get a "OutofMemory" exception?
 
Back
Top