on 11-10-2009 6:30 PM
Hello Experts!
I have developed an application for my mobile client on handheld, but i have a problem with performance, my problem is on load of client, elapsed time to load this ambient is 25 seconds, somebody have a solution to increase a performance to load Mobile client on handhelds?
Regards
Ronaldo Rampelotti.
Hi Ronaldo,
The first time the client is launched after application deployment the intial time is high as we install the client that time.
Post the first time subsequent start of clients should be faster.
In case there are issues with the intial load in the application then you need to do some optimizations in the app code to have a better performance.
please note that if you would be firing all your queries at the start up of application then intial load will be high. Execute the queries only when needed, only fire necessary queries at start up in the component controller.
Also using DB2e will be beneficial for a better performance.
Do not model heavy views with lot of UI elements, try to break down the use case into multiple views. LIke List view & detail view.
Please see to the above points and check against the application.
Regards,
Nipun
PS: Recommended flash ROM is 128 MB & RAM is also 128 MB.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nipun,
I launch my ambient more than twice time, i put arguments on MI how user and password, so when they starts, start logged, i have new time for my startup: 2 minutes, it is to slow.
It is my specification:
CPU: Marvell PXA270 Processor 312 MHz
Mem: 192 MB ROM and 64 MB SDRAM
SO: Microsoft® Windows Mobileu2122 5.0 for Pocket PC, Premium Edition
I will just display a popup for the User to know what is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Someone help?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My device's specifications
MC9090
- WM 5.0
- ARM 624 MHZ
- 64/128MB memory
On the 64MB, it is less than a minute to load from executing the NWM shortcut (post first time initialization) and auto launches into a WDP application.
Admittedly, I have removed all unecessary applications from the /Windows/startup folder to optimize resources and tweaked registry settings for cache, not really sure if it has helped or not.
Even with less than a minute, our end-users complained.
One thing would be to change the argument for MI client to displayPopup=true, so at least end-user can see that the MI client has started, and it is loading and it is not a mystery for 2 minutes whether the application is starting or not.
you can make that change in launch.properties under the MI\bin folder
Thanks for reply!
I will try to do it, only for the user can see a window, but the performance at first time is expensive, we have to consider the application starts one time for lifecycle to use, so the expensive time is one time on day, it is not affect directly the rule of bussiness and end-user does not see it more one time per day.
Best regards, Ronaldo.
I was given this a long time ago back when I was developing on SP3
Not sure if they are all valid or more have been added.
I thought I posted this awhile ago, but can't find it maybe it got deleted.
These CSS properties are ALL or NONE, you cannot specify by View or by some class id.
I think there are suppose to be improvements in next version of MI client.
Name of the property
default
stylesheet.default.backgroundcolor
stylesheet.default.foreground
stylesheet.default.font.name
stylesheet.default.font.size
stylesheet.default.height
stylesheet.default.bordercolor
brandingarea
stylesheet.brandingarea.backgroundcolor
stylesheet.brandingarea.bordercolor
stylesheet.brandingarea.font.size
stylesheet.brandingarea.foreground
stylesheet.brandingarea.height
stylesheet.brandingarea.brandingtext
button
stylesheet.button.backgroundcolor
stylesheet.button.font.size
stylesheet.button.foreground
stylesheet.button.height
label
stylesheet.label.backgroundcolor
stylesheet.label.font.size
stylesheet.label.foreground
stylesheet.label.height
caption
stylesheet.caption.backgroundcolor
stylesheet.caption.font.size
stylesheet.caption.foreground
stylesheet.caption.height
inputfield
stylesheet.inputfield.backgroundcolor
stylesheet.inputfield.font.size
stylesheet.inputfield.foreground
radionbutton
stylesheet.radiobutton.radiobutton
linktoaction
stylesheet.linktoaction.backgroundcolor
stylesheet.linktoaction.font.size
stylesheet.linktoaction.foreground
stylesheet.linktoaction.height
statusbar
stylesheet.status.backgroundcolor
stylesheet.status.errorcolor
stylesheet.status.messagecolor
stylesheet.status.warningcolor
table
header
stylesheet.table.header.backgroundcol
stylesheet.table.header.foreground
stylesheet.table.header.height
stylesheet.table.header.font.size
content
stylesheet.table.content.backgroundcolor
stylesheet.table.content.foreground
stylesheet.table.content.height
stylesheet.table.content.font.size
footer
stylesheet.table.footer.backgroundcolor
stylesheet.table.footer.foreground
stylesheet.table.footer.height
stylesheet.table.footer.font.size
imagebutton
stylesheet.imagebutton.backgroundcolor
stylesheet.imagebutton.font.size
stylesheet.imagebutton.foreground
image
stylesheet.image.backgroundcolor
I don't know about the client arguments, usually that was a guess\try and find out.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.