[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference eusact::sap

Title:SAP-Notes
Moderator:OSTV03::NAKAYAMA
Created:Mon Nov 09 1992
Last Modified:Wed Feb 26 1997
Last Successful Update:Wed Feb 26 1997
Number of topics:735
Total number of notes:2563

727.0. "Batch input load model?" by TIMAMD::CASTILLA () Thu Jan 23 1997 22:53

T.RTitleUserPersonal
Name
DateLines
727.1close to the impossibleATZIS3::WINTERSPERGEMon Jan 27 1997 16:1253
    Hello !
    
    You can somehow rape the syssizer tool to give you a wild guess on if
    that is possible. First try to find out how many transavtions such a
    batchinput will trigger (you can look at the input map within SAP,
    but for this you need probably more knowledge then you have).
    
    So you can guesstimate that 1 booking will be something like 2-3
    (maybe 4) transactions. This then means in your case 
    about 1.8Mill transactions. Divided by the acceptable time this would
    mean something like 300.000 transactions per hour.
    
    You then have to know in how many maps you can split the stuff
    (worst case only 1) and add this numer for the users. Then
    you change the transaction rate until the number in the right botton
    corner matches the 300.000 
    
    If you then ask for a machine you will find out that this is even
    beyond what an Alpha (and every competition) can do (the maximum is
    about something like 200.000 transactions). 
    
    Be also aware that if for example the sizing tool suggests much more
    CPUs then you have batchinput maps this will not work, because they are
    not so parallelizable.
    
    Forget also the memory calculation of the sizing tool in this case.
    
    So as outlined above you can use the tool only for getting a raw idea
    what size the machine will be in this case.
    
    I would suggest to extrapolate from one of my customers in Austria. He
    has a 8200 with 4x440MHz CPUs and 1.5 GB Mmeory arunning 2.2 of SAP
    and he gets close to 40.000 standard FI bookings (not transactions) 
    per hour. This customer already does creative things like running the
    Oracle logfiles on a Solid state (RAM) disk during this periood and you
    have also to turn off some SAP features (like deleting the Updatelog)
    during this time.
    
    And be aware the 4th CPU is almost idle, even when he runs about half a
    dozend maps at the same time.
    
    So he would be able to do 600.000 in about 15h which is about twice the 
    time you are looking for. 
    
    So in your case the customer will have to look into the 
    new 'fast' batchinput procedure SAP offers with 3.0
    which can give a 200-300% performance increase (at least SAP says so)
    
    I hope this gives you some ideas on how to proceede, generally 
    said it probably will end up in a try and see approach.
    
    				Regards
    				Thomas Wintersperger, Austria