4 Replies Latest reply: Apr 29, 2013 3:03 AM by Anuj Dwivedi--Oracle RSS

    B2b mds cache impacting bpel performance

    svswin
      Hi All,

      We have xmx set to 4GB and we have set the b2b.mdsCache to 400 MB.

      Our process runs as JMS --> B2B --> JMS --> Composite app(mediator and BPEL)--> OSB

      In composite application in one of the step mediator publishes events to EDN.

      Now when we dont have B2B MDS cache set to 400 MB, The composite process completes within a second

      But when we have b2b mds cache in b2b-config.xml set to 400 MB then the composite app takes 20 sec to complete. when we analyzed this we found that mediator is taking 10 second to publish the even to EDN which inturn increasing the over all processing time as message is being published to END twice in this composite app.

      Even subscribing to event is very slow almost 9 sec.

      Env Details :
      Soa 11.1.1.5 on linus 5.1, in dev mode with default settings
      xms - xmx = 2GB - 4GB

      We set the b2b.mdscache to 400 mb as per the Oracle doc as below:

      A ratio of 5:1 is recommended for the xmx-to-mdsCache values. For example, if the xmx size is 1024, maintain mdsCache at 200 MB

      Regards
      SVS
        • 1. Re: B2b mds cache impacting bpel performance
          Anuj Dwivedi--Oracle
          Do you really have a huge B2B repository? What is the size of your entire B2B repository (export it to know the size)? What volume of messages do your B2B process in an hour during peak time?
          We set the b2b.mdscache to 400 mb as per the Oracle doc as below:
          Please remember that these settings should be changed only when you see any issue related to performance. By default B2B assigns 200MB for MDS cache which is sufficient enough to handle fairly large configurations.
          In composite application in one of the step mediator publishes events to EDN.
          Is your EDN JMS based or DB based?
          But when we have b2b mds cache in b2b-config.xml set to 400 MB then the composite app takes 20 sec to complete.
          First of all, this property is set in the EM console. b2b-config.xml was used before 11.1.1.3. To understand that why EDN is taking 20 sec, take multiple thread dumps of your server while processing EDN message and also generate an AWR of your DB. This will give some idea that where delay is happening. Also monitor the heap usage and CPU usage during this processing.

          Regards,
          Anuj
          • 2. Re: B2b mds cache impacting bpel performance
            svswin
            Hi Anuj,

            Thanks for you response. Please find the details below:
            Yes we are setting cache property from EM console.

            1. B2B repository export size for active agreements - 3 MB

            2. EDN - its DB based and based on the AWR report there are lots of DB operation so we are planning to move it to JMS.

            Can you tell us why B2B MDS cache is impacting, publishing events to EDN from BPEL process.

            We reduced the MDScache to 200 MB and the B2B performance goes down but Publishing events to EDN has improved than earlier when cache was 400MB

            We have also set B2BMDSCache.minutes to live to Zero.

            Regards,
            Surendra
            • 3. Re: B2b mds cache impacting bpel performance
              Nitesh Jain
              You can try with 200 MB itself.

              To improve the B2B performance, you can redeploy all the agreement from Deploy page of Administration in a single shot.
              Deployment should be in single unit. means select all and deploy.

              Then remove all the inactive agreements from the manage deploy page of Administration.
              This will help in improve the MDS performance.

              Let us know the TP and agreement counts.
              What is the performance are you looking from B2B.
              • 4. Re: B2b mds cache impacting bpel performance
                Anuj Dwivedi--Oracle
                Hi Surendra,
                1. B2B repository export size for active agreements - 3 MB
                Then no need to tune the B2B MDS cache. Leave it to the default value (200 MB).
                2. EDN - its DB based and based on the AWR report there are lots of DB operation so we are planning to move it to JMS.
                Have you noticed any change in SQL's or their execution plans when you increase the B2B MDS cache to 400MB?
                Can you tell us why B2B MDS cache is impacting, publishing events to EDN from BPEL process.
                Don't see any reason why B2B MDS cache should impact EDN. May be server does not have enough resources or DB is having some issue. Better log a SR with support and find the root cause. It's least probable but you might be hitting a bug in the product.

                Regards,
                Anuj