Hi,
I am using Jdev 12c and I have a particular database with millions of rows. All my application tables have Scroll policy set to "Page". Now I am not sure but it seems that if I go to last page in my table all the rows get cached in my memory. So if there are more than one instance of application running, it becomes really heavy on Server memory and I start to get memory related exceptions.
I am looking to improve performance of the VOs and reduce the load of tables/application on memory as suggested in several posts. I tried playing with VO tuning parameters. But setting AccessMode to "RangePaging" or "RangePaging Incr" gives odd results on the table. eg I just see the result from first page even when I am changing the pages on the table.
I haven't seen any post till now which plays with Tuning parameter while scrollPolicy is set to "Page". Are there some known issues related to that or am I missing any other aspect of improving performance of VOs? Also, is ScrollPolicy Table property somehow effects how Tuning parameters are supposed to be defined for VOs?
Thanks!