neil_shepherd
Well Known Member
Hi,
I'm interested in finding out if anyone's made changes to the database cache settings as defined in P98613, and in particular if you've been able to measure the changes (not an easy thing on a busy system), and were they worth it? For a number of our truely static tables e.g. F0025 ledger types, I'm thinking of increasing the rows to match our current record count. Can't see this being a problem through wondered if any positive gain is to be had.
On the other side of this I see the address book and exchange rate tables are also included, though the knowledge garden records some issues around the F0101 and indicates it removal from later releases. My problem with this is if a field is changed by user A then user B will not pick this up until they log off and on again. Maybe not a huge issue but something to be aware of. Has anyone removed the F0101? Did you notice any negative impact?
Regards
Neil.
I'm interested in finding out if anyone's made changes to the database cache settings as defined in P98613, and in particular if you've been able to measure the changes (not an easy thing on a busy system), and were they worth it? For a number of our truely static tables e.g. F0025 ledger types, I'm thinking of increasing the rows to match our current record count. Can't see this being a problem through wondered if any positive gain is to be had.
On the other side of this I see the address book and exchange rate tables are also included, though the knowledge garden records some issues around the F0101 and indicates it removal from later releases. My problem with this is if a field is changed by user A then user B will not pick this up until they log off and on again. Maybe not a huge issue but something to be aware of. Has anyone removed the F0101? Did you notice any negative impact?
Regards
Neil.
