VO Fetch Size : data queried from the database to the business service within a single round trip
rangeSize : Data queried from the view object cache into the binding layer. If range size exceeds fetch size then the VO issues two fetches
So, let me ask another question about rangesize. What is the difference between rangeSize parameter in view object tuning section with the rangeSize attribute of the iterator binding behind a page? I was supposing that what you declared is for rangeSize attribute of the iterator binding.
And the second question is that it seems that the important parameter for performance is Fetch Size which determines the number of roundtrips, not rangeSize. Is that true?
1 person found this helpful
The range size in the vo is only used when your vo uses one of the range paging modes to get the data. Here you normally use scrollable, in this case this parameter isn't used.
Second question you are right. Fetch size it's the parameter to set.
From oracle’s documentation we learn that RangeSize attribute of the Iterator “controls the number of records ADFm requests from the BC layer simultaneously”
This parameter controls the number of records ADFm requests from the BC layer
simultaneously. The default RangeSize is 25 records. Consider setting this value to
the number of records to be displayed in the UI simultaneously for the View Object so
that the number of round-trips between the model and BC layers is reduced to one.
This is configured in the Iterator attribute of the corresponding page's page
and the purpose of FetchSize is now clear for me but let me ask another question about VO’s rangeSize which you told is used when we use range paging. You mean that when we use range paging so the rangeSize of VO is used to fetch data from database and the FetchSize is ignored in this case? Please correct me if I am wrong.
Thank you very much, the link you sent helped me a lot