1. Christopher Craft
  2. PowerBuilder
  3. Tuesday, 5 June 2018 20:35 PM UTC

Looking for some input as to what exactly this setting does and why you would not always just set it to Large?  I have customers that run into an issue where if the report is too large it will just crash because it has exceeded the memory. I am wondering if this setting will help in that area. I would expect it to return a -1 in the Retrieve but it just explodes instead.

Thanks for the input!

Chris Craft

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 5 June 2018 21:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris;

FWIW:     I just tried this with my framework and a small test window & DWO combo that I used, still uses 6,464 bytes of memory regardless of whether I set the StoragePageSize to "medium" or "large". However, the DWO retrieval time is 10-20ms seconds better when in "medium" mode setting. We would have to do more studying of this feature to get more information. I suspect that Sybase never really documented it. Maybe this was even a PowerSoft feature way back when?

HTH

Regards ... Chris

Comment
  1. Christopher Craft
  2. Wednesday, 6 June 2018 21:38 PM UTC
Thank you Chris. I wonder what those settings would do if the retrieved rows was enough to make the DW storage 500 MB?

  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 6 June 2018 22:01 PM UTC
Good question ...  Looks like you would have to test that setting under extreme load (aka large result set) and see what happens.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.