Msync- Processing Phase

Question

Hi all,
When sync large amount of txn Processing phase takes a longer time in the client.(Composing ,sending and receiving is withing the acceptable timing)
1. What exactly happens during the processing phase of client side?
2. If the issue is clients do not have a large memory for the process phase ,is there any way to issue some kind of commit for rows for it to release memory?
3. Overrall how to speedup the processing phase of the client?
Thanks
Paninie.

Answer 1

unfortunately i do not know in such depth the way that the transactions are commited. and i dont think that i have read anything
about this in the documentation (about commiting each number of rows).
we are using windows mobile 6.1 with the latest olite updates (hope you use the latest updated cab files for the client ).
well concerning the sd cards we have tried with a mini sd card (2gb) -i'd better not say the brand name cause i dont want to appear to be selling anything, and a micro with a mini adapter(2 gb also). the micro is slower than the mini in the processing time of a simple synch, and much more slower in the first synch where the database is created. the mini sd card takes about 40 minutes to create the database in the first sync in our application whereas the micro takes about 2,5 hours. in a normal synch where no updates are applied, the mini sd is about 2 secs faster in the processing (the mini takes about 5-6 secs in this case).
we have used a freeware tool to test the speed of each sd card. try testing diffrent sd cards. you can also try to save the database in the
main handheld's memmory (which is much much faster) but in our case there isnt enough space for that and we are obligated to use a sd card.
one thing that i am sure that you can do is to create your own application (e.g. in .net and use the synch class ) in order to synch one publication item/table at a time. for example synch customers table first , finish and then synch another one. of course this means that you will connect many times to the server to send the data but you will perform a subset of txn at each time.
e.g.
using Oracle.DataAccess.Lite;
String args = "username/pass@serverurl/onlytable:Customers";
OracleEngine.Synchronize(args);
are you getting any out of memmory exception message when synching? we used to get those when we were sending 250k of rows to the client in one table and then we decided to split the table in more tables of 50k each. once we got that message everything appeared to be crashed and we couldnt open not even msql unless we restart the handheld (olite didnt use memmory correctly apparently). but now with the splitted tables everything seems to be going much better.(especially the index based search)