App Connect

 View Only

  • 1.  high resource consumption in CP4I for ACE

    Posted 25 days ago

    Hi,

    A same project consumes much higher resource in CP4I setup compared to standalone VM based setup. The higher resource consumption increases license. This analogy I am sharing based on my experience. Is the observation correct or there is something wrong? What are the best practices for deploying BAR files in CP4I setup for minimal resource consumption? 



    ------------------------------
    Nitish Sinha
    ------------------------------


  • 2.  RE: high resource consumption in CP4I for ACE

    Posted 24 days ago

    This has not been my experience, and I have setup ACE in OCP for dozens of customers over the past 2 years.   You also need to compare the CPU that you are using for ACE in a VM vs the virtual CPUs used in ACE in OCP, they are different.  In fact, customers have been saving money because they do no have to over allocate the CPU and memory if there is a spike in OCP, thus saving money month to month.

    Brian



    ------------------------------
    Brian S Paskin
    Sr. Technology Engineer
    IBM Cloud Engineering
    ------------------------------

    Original Message


  • 3.  RE: high resource consumption in CP4I for ACE

    IBM Champion
    Posted 21 days ago

    Hello Nitish,

    I've encountered the same issue. In my experience with CP4I, the memory shown is the allocated memory, not necessarily the memory currently in use, but what has been used. To optimize resource usage, try removing unused parsers and unnecessary loops from your flows. Additionally, consider clearing the environment after the flow completes by using DELETE FIELD.

    Keep in mind that parsers are not automatically removed after use. If you have many parsers, this can lead to higher memory consumption.

    Also, if you have big lists, try to sort them, so you don't have to loop over them, this decreases the CPU usage a lot.

    Regards,

    Kjetil Svihus

    IBM Champion



    ------------------------------
    Kjetil Svihus
    ------------------------------

    Original Message