Skip to Content
avatar image
Former Member

Regarding the sizing output in Quicksizer

Hi,

I am doing a sizing for Netweaver 7.0 PI implementation. I need help on interpret the results. I have got the input from functional team and have entered according to their inputs but now it is difficult for me to convert it according to our IT team requirement?

I got the below results.

1. SAPS: 2.000 - Processor: S

How to convert this to equivalent number of processor cores and the required processing speed in mhz.

2. DB Disk Category: XS

How to decide the hard disk size in GB?

Do we need to add the disk required for installation along with this output or this includes both installation + application requirement?

This disk sizing is considered for how many years data growth?

3. Memory: 6.144 (In intervals of 256 MB)

How to convert this value to a RAM of particular GB?

Expecting your help on this.

Regard,

Nalla.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 14, 2009 at 04:38 AM

    You may want to check SAP note 85524 and relevant note in this note. BTW, did you check with hardware vendors?

    You may also want to attached guide

    [https://websmp209.sap-ag.de/~sapidb/011000358700000523272005]

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 15, 2009 at 03:40 PM

    I do a lot of sizing for various customers and generally use certain rules of thumb.

    First what architecture are you planning to use?

    x86

    Itainium

    Power

    Sparc

    Then goto www.sap.com/benchmark and look at the two tier SD benchmarks

    and find the hardware that is closest to what you want to use?

    2000 SAPs is not very much these days if you look at current HW architectures.

    If you look at current Benchmarks you'll see 2 way Nahalem x86-64 processor

    (4 cores per socket) gives about 17000 SAPs so that is roughly 2125 SAPs per core.

    So in this case you'd only need 1 physical CPU core. However SAP is a highly parallel

    application. If you only have one core available a large interface/job could load a single core to

    100% stalling anything else so you'd really want to use either two physical or two virutal cores.

    Then the rule of thumb is generally 4GB Ram per CPU core.

    In terms of disk. PI does not store much data (mainly logs). Again disk is very cheap these days

    .5TB should last you years.

    It's a pity oracle is still not certified for productive use in a production environment under VMWARE/Xen as you will have rather alot of spare capacity in the above scenario

    Add comment
    10|10000 characters needed characters exceeded