Consuption of memory on PDA wih SAP Mobile 7.1

[Former Member]

Hi all,

We have some problems with usage memory RAM in device, with the client SP8 (and others). Any idea or solution?

Thanks,

Roberto

[Former Member · Accepted solution]

Hi Roberto,

I feel that the application is consuming too much memory and needs to be improvised.

Here are some suggestions to improvise the application:

• It has been observed that performance improves significantly when db2e Database system is used.

• In the service component, avoid using DataObject node as the output of the query result.Instead use datastructure and map only those attributes which are required and leave those not required.

• Every OCARoot.commit() is expensive hence avoid it where ever possible for ex: Call commit() after updating many rows instead of calling it after updating one row.

• Reduce the number of items in a single page as each items increases the overhead.

• In UI Component, Use Component Controller context only when the context has to be shared across multiple views.Directly map view context to data model elements when the context need not be shared between view.This avoid overhead of creating Component controller context and the binding of the view context to CC context.

• Import only those model classes in UI component which are required in the UI Component.Skip the remaining model classes.

• In the UI component, avoid loading views from another UI Component.Dont split each view into separate UI component.It is recommended to have as much View in a single UI component as possible instead of splitting the views between UI components as it is costly to navigate between views of separate UI Component.

• In UI Component, Avoid holding the query results in the context node or in a member variable in the component controller if it is no more required.

• In UI Component, Its a good practice not to use multiple tabs or transparent containers inside a single view. Its always advisable to break the tabs into different views and use minimal number of transparent containers.

• In Service Component, Use 'Bidirectional' for all the queries.

I hope this helps.

Best Regards,

Amit

[Former Member]

Hi

Please check this PDF link

http://www.sapexperts.com/index_of_articles.pdf

Regards

Ruturaj

[Former Member]

Can you give us more details on your Memory issue and mobile device (Processor\RAM\OS)?

Is it just from regular usage with the developed application?

or is it noticeable from going into the Synchronization view back to Application Launcher?

I am just curious, as we are experiencing Memory consumption issues too, we are trying different approaches but have not found a solution.

[Former Member]

Hi Alan:

We use a ppc with 128 Mb RAM, procesor ARM92OT PXA27.

We are testing with Windows Mobile 5 and Windows Mobile 6.1 but the result is the same.

Yes, it is only with the own application. When we sync (SAP Mobile Client 7.1 SP8) the memory is the same, only change about 0,1 MB of RAM.

If we use the app, memory ups continuosly, until the limit.

We try to reduce the elements, images, but... nothing.

Thanks for your response.

Roberto

[Former Member]

Hi Roberto:

We use Motorola\Symbol MC9090 PPC with 64 MB device (Intrinsically Safe) and 128MB (non-intrinsically safe).

All on WM5.

We were thinking of going to WM6 given that other mobile forums state memory management improvement in WM6, but we were told that the WM6 o\s was not supported by SAP.... I have used a PC emulator with WM6 image with MI 7.1 SP7 PL05 but did not see any noticeable difference\improvements.

To hear from you that there is no difference between WM5 and WM6 seems to confirm that experiment.

We have deployed a mix of 7.1 SP03 PL09 and 7.1 SP07 PL**

Our business scenario is 24x7 continuous usage, and the only application that should be used by the end-user is the SAP MI Client running the developed WD application.

We have stopped or deleted any unnecessary applications from loading on startup or in background.

Our 64MB usually only last a few hours ( a couple hundred VIEW loads\OCA commits) before all memory is consumed and the mobile device must be rebooted.

Our 128MB devices can usually last a few months and rarely crash.... as far as I know.

I have been investigating the memory consumption issue in efforts to stabilize the 64MB devices.

Do you use the eSWT for presentation? or awt or jsp component?

We use eSWT and have CustomControls for enlarged fonts\custom colors for input boxes\tables etc...

I believe SAP is providing eSWT 1.0.

I suspect for us that eSWT+Custom Controls could be the problem. I have had some difficulty in researching eSWT.

So no hard evidence saying it is eSWT, I have used this application called Best TaskMan to analyze the memory and have noticed a lot of hidden windows are created in the background as you use the MI client.... but it is difficult to know if that is the reason.

I have been given tips:

- reduce Transparent containers

- reduce variables

- nullify references to context

and after days of going through all the Views, I did not notice a significant improvement.