willbewill

Anybody know whether dbcache is beneficial to TX - I've loaded it but it doesn't seem to make any difference, in fact I have had a couple more resets - also any comment on Rlock?

Chukar

In my experience, neither one does much good.

palmdoc88

I have given up using Rlock. I just use dbcache, db clear type, auto off, always clear on soft reset. That way after a soft reset, I clear the dbcache and I get 11MB on my Treo650. Good to start the day with a large dbcache free.

__________________
Palm for life....

janos

In theory TX should be a lot different than the older models.

Locking might not work anymore, but it might not be needed anymore as well.

The point is that Palm does not respect locking state when deciding which apps will be flushed from the DbCache, but it does respect some other calls that are traditionally issued by the background apps and these calls should effectively lock these apps in memory. (This works only for TX.)

I must say, I did not verify it.

Once more, in theory TX should do better without any extra tool than the previous models with extra tools.

Best regards

__________________
Jano

hihostevo

I just bought my wife an Tungsten E2 with GPS for her to use with her Real Estate work. I got the (TomTom 5) Navigator software to run once and then after looking up an address in the Palm I get the following message “Not enough free DB Cache Memory to run this application.”

My Internet information search brought me to this forum...

If you have any suggestions I would love to hear them, because I am completely lost at this point… and the TomTom people do not have a phone number for tech support. They will email me back in 2 to 3 days however… so kind and considerate don’t you think?

janos

Hello,

I can just explain my point of view, the reaction is upon you.

DbCache is a window approx. 10MB large (size is HW depending), through which RAM databases are accessed. These DBs are otherwise located in NVFS memory which is accessible only to the OS.

DbCache works like a cache. Whenever a request for reading/writing to a DB comes, part of that DB (the affected records) are moved into DbCache. If there is not enough space, some older unused records are purged from DbCache to provide the space.

This mechanism has one important exception: Locked records stay in the DbCache permanently and cannot be purged until unlocked.

Applications lock records because they want to process them. This typically creates temporary locks.

Permanent locking happens if
a) App forgets to unlock the record
b) The record is not unlocked with purpose - e.g. to prevent crashing a background application that is not NVFS-aware.


“Not enough free DB Cache Memory to run this application.”
This looks like TT failed to reserve (i.e. lock) part of this memory for its purposes.

I suppose that TT did enough testing to know that they can run on E2 under normal occasions. If this is true, then the only explanation is that you use other apps that take too much DbSpace and do not return it back. (Either with purpose or by a mistake.)

Try
1. Run TT as soon as possible after a reset.
2. If this does not help, try to disable some active background processes.
3. You can investigate locked records also more rigorously:
Install Resco Explorer.
Go to RAM folder.
Context menu (opened through a long tap): Select Special filter > Show locked
Each locked DB can be opened (View icon in the toolbar). Then the record selection combobox indicates the locked records through a suffix Ln. (n=1,2...)

If you have a deeper knowledge about Palm OS, you can probably identify the reason this way.

You might discover this way that the locked space is too large. In this case try to identify the excess records. (Either forgotten locks or background apps that could be disabled.)

But you may also discover nothing. In this case the problem will be probably the fragmentation of the DbCache through locked records. This could happen if TT tried to lock some large records. (This might be the case as they probably use some huge ARM code records from the PPC version.)

Best regards

__________________
Jano

romeosg

Just curious if DBCache Tool is still required for T5's with the 1.1 Upgrade?

mick711

hello

What is your parameters for DbCache tools for palm T5 please ?

the DbCache in my T5 with rescoexplorer is 6770ko
rom 12224ko
max Dyn Shunk 3226ko
max Stor Chunk 16383

Dyn 3299/4096
Stock 32234/65386

edit : DbCache 6770ko

I upgrade my T5 with the patch 1.1

thanks

janos

At this instant my parameters are:
DbCache 9789K
rom 12160
MaxDynChunk 3295
MaxStorChunk 14018
Dyn 3384/4096
Storage 14018/65386

After running Backup/Verify I got the same numbers (a positive sign) except DbCache that decreased to 2660.

You see, the actual DbCache number changes. It is simply amount of the free space in the cache. If this number is too low, system will remove some unneeded data blocks and free thus additional space.

The only meaning of this number is that if it is low, than some DBs might start moving. This is nothing wrong unless you have a background application that is not prepared for DB moving and unless this app gets really moved. (The decision is up to Palm OS.)

If all your apps behave well, you may ignore DbCache size.

Jan SLodicka
Resco

__________________
Jano

mick711

Ok

but with tomtom5 or viamichelin4 softreset after run program because dbcache full !

How can i parametr dbcache ?

please because the vupdate 1.1 of palm is not the solution.

thanks