Ansicht
Dokumentation
08846 - Export/Import buffer size
ROGBILLS - Synchronize billing plans ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Export/Import buffer size
It might help to understand more about how the buffer is used.In abap, a function module has its own memory space. When a function module is
called, the parameters are exported to memory and imported into the function
module. The function module then does what it needs to do and exports the
returned data back into memory. This memory is allocated in export/import
buffers.
A function module has these parameter types: Importing, exporting, changing,
and tables. Usually, importing, exporting, changing parameters are relatively
small which is why you see allot of entries with less than 782 bytes. The
tables can get relatively large.
This becomes more important in 4.5 and very important in 4.6B and C. There is
something called an ABAP list viewer or ALV control that you will see more and
more on screens in 4.5 and later. They are really great because they are
flexible. Users can rearrange data, sort, print, spit, whatever. The ALV
control is implemented as a set of function module calls. So...
When a user brings up allot of data into one of these ALV controls or sends
allot of data to a function module in a table, this export/import buffer can get
used up and start swapping. So, to account for users/abusers who bring back
more and more data, I set the largest object size to be 4096K or 8192K and make
sure the buffer is large enough to hold at least 2 of these. That usually
eliminates most of the swapping and improves the application performance for the
function calls.
Hope this helps.
Best regards,
Alan
-----Original Message-----
From: Jim Doll [mailto:jdollZperrigo.com]
Sent: Friday, January 10, 2003 10:42 AM
To: DoNotReply@consolut.eu
Subject: Export/Import buffer size
I've been working on adjusting our "export/import buffer", but it has 3
parameters instead of the usual 2:
rsdb/obj/buffersize = size of buffer
rsdb/obj/max_objects = number of directory entries
plus
rsdb/obj/large_object_size
Is the last one truly the "largest", or should it be the average, or maybe the
size of most of the objects?
When I view the buffer on my dialog instance, I have 6,344 objects total, and 4
of them > 450,000 bytes. But the majority of them are less than 782 bytes.
My directory seems fine. I've been experimenting with both the buffer size and
the size of the largest object, but I'm hesitant to do much more with the
largest object setting without more information, which I can't find via RSPARAM
or from OSS. Or maybe it just isn't practical to eliminate "swaps" in ST02 in
this buffer?
Current dialog settings are
rsdb/obj/buffersize = 25,000
rsdb/obj/max_objects = 30,000
rsdb/obj/large_object_size = 49,152
Current batch settings are
rsdb/obj/buffersize = 75,000
rsdb/obj/max_objects = 20,000
rsdb/obj/large_object_size = 81,920
Running 4.6C on 840 with V5R1.
Thanks in advance for any input.
Jim Doll, Perrigo
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
Fill RESBD Structure from EBP Component Structure RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 4149 Date: 20240601 Time: 234434 sap01-206 ( 3 ms )
