Automic Workload Automation

  • Private Community
Back to discussions
Expand all | Collapse all

AE & AWI sizing

  • 1.  AE & AWI sizing

    Posted Nov 20, 2017 09:03 AM
    Edited by Michael A. Lowry Apr 03, 2023 06:23 AM
    In a recent discussion about poor AE performance following DB load of transport case, the topic of AE sizing came up. As we plan a future switch from the Java User Interface to the Automic Web Interface, we also are interested in learning more about the sizing requirements for the AWI.

    We plan to migrate from the JUI to the AWI in the coming year or so. Eventually, there could be a couple hundred AWI users connected simultaneously. Simultaneous with this change from JUI to AWI, we will also be switching from the transport case to XML for AE object deployments.

    With these two upcoming transitions in mind, when I look over the sizing recommendations, a few points stand out:
    • For up to 200 users, the AWI needs 32 GB of RAM.
    • To handle 200 connected users, about 100 DWPs would be required.
    • If large workflows are used, the AE & AWI need an additional 1-2 GB per DWP.
    • If large XML exports/imports are performed, the AE & AWI need an additional 1-2 GB per DWP.
    As I understand these requirements, if we have 200 connected users, use large workflows, and perform large exports/imports, then we will need between 232 and 432 GB of RAM for the AE & AWI.

    Base
    requirement    		 + Supplement for
    large workflows
    		 + Supplement for
    large XML imports/exports
    		 ≈ Total RAM
    requirement
    Low estimate
    32 GB
    		 + 100 GB + 100 GB ≈ 232 GB
    High estimate 32 GB + 200 GB + 200 GB ≈ 432 GB
    Is this correct? Is it realistic? Do both the AE and AWI need this much RAM?


  • 2.  AE & AWI sizing

    Posted Nov 20, 2017 10:23 PM
    Hi

    Michael A. Lowry



    Are you going to install AE and AWI on the same server? and all DWPs on the same AE server?
    I think not.
    Please note that the document recommend the Memory size for the server where you install the component.
    So you will not need that much memory for one server...

    Best regards,
    Hoai


  • 3.  AE & AWI sizing

    Posted Nov 21, 2017 03:56 AM
    Edited by Michael A. Lowry Apr 03, 2023 06:24 AM
    Hoai_Truong-Thi-Thu_5649:
    I direct your attention to this section from the documentation (emphasis mine):
                                                           

    Do you expect huge workflows (> 1000 tasks per workflow)?

    		                    

    No: -
    Yes: Add memory toAE/AWI (expect 1-2 GB per DWP)

                   
                       

    Do you expect huge xml imports/exports?

                       		                    

    No: -
    Yes: Add memory toAE/AWI (expect 1-2 GB per DWP)
    Perhaps you can clarify whether memory must be added to the machine running to AE, the one running the AWI, or both. Thanks!


  • 4.  AE & AWI sizing

    Posted Nov 27, 2017 08:37 PM

    Michael A. Lowry


    Yes, you are correct. The additional memory should be added to both AE and AWI.
    However, the provided number is for reference.
    We should adapt to the real system/situation.

    And all in all, always test before put it to production.

    Br,
    Hoai


  • 5.  AE & AWI sizing

    Posted Nov 28, 2017 05:23 AM
    Hoai_Truong-Thi-Thu_5649: Thanks for your reply. That confirms my reading of the text.

    Here is the challenge we face:
    • A small number of users will work with very large workflows, but most will not.
    • A small number of users will perform large XML imports & exports, but most will not.
    • We want to make it possible for the users who need to be able to work with large workflows or XML files will be able to do so.
    • We do not want to have to allocate hundreds of gigabytes to the AE & AWI servers unnecessarily.

    Do the recommendations regarding huge workflows & XML files pertain to average usage or peak usage? In other words, do we need to ensure that every DWP has an extra few gigabytes available, even if only a small number of users will work with huge workflows & XML files?

    Thanks in advance if you can shed additional light on this topic.


  • 6.  AE & AWI sizing

    Posted Jan 24, 2018 08:52 AM
    Would anyone from Automic_Community_5543 possibly be able to help answer the above questions? Thanks in advance.


  • 7.  AE & AWI sizing

    Posted Mar 05, 2018 03:35 AM
    I opened REQ00221120 to get definitive answers to these questions.


  • 8.  AE & AWI sizing

    Posted Mar 08, 2018 11:52 PM
    Michael Lowry said:
    Hoai_Truong-Thi-Thu_5649: Thanks for your reply. That confirms my reading of the text.

    Here is the challenge we face:
    • A small number of users will work with very large workflows, but most will not.
    • A small number of users will perform large XML imports & exports, but most will not.
    • We want to make it possible for the users who need to be able to work with large workflows or XML files will be able to do so.
    • We do not want to have to allocate hundreds of gigabytes to the AE & AWI servers unnecessarily.

    Do the recommendations regarding huge workflows & XML files pertain to average usage or peak usage? In other words, do we need to ensure that everyDWP has an extra few gigabytes available, even if only a small number of users will work with huge workflows & XML files?

    Thanks in advance if you can shed additional light on this topic.
    Hi Michael,

    I believe  we wouldn't need to allocate few hundreds gigabytes to the AE (for every DWP)  and AWI since most of your users are not handling huge task, the  resource will be auto balance between each DWP, and tomcat/AWI also using memory pool so It gonna be shared between users as well.
    I would suggest to test and tuning.


  • 9.  AE & AWI sizing

    Posted Mar 09, 2018 03:41 AM
    Tran-Hoang_Hau_348: Thanks for the update.

    I understand from your response that the DWPs and AWI server only momentarily require extra memory when they are performing memory-intensive operations such as:
    • Imports/exports of “huge” XML files
    • Handling workflows with more than 1000 tasks
    Is this understanding correct? If so, I have two follow-up questions:
    1. What is a “huge” XML file? (30 MB is the maximum size currently allowed, and that does not seem particularly large to me.)
    2. Could you provide us with an SQL query to help us identify workflows that have more than 1000 child tasks? (What is the maximum number of tasks permitted in a workflow?)



  • 10.  AE & AWI sizing

    Posted Mar 12, 2018 12:18 PM
    I wrote an SQL query to list workflows containing more than 255 tasks.
    select max(JPP_Lnr), JPP_OH_Idnr, OH_Name
    from JPP join OH on JPP_OH_Idnr = OH_IDNR
    where OH_DeleteFlag = 0
    and OH_Client = 1
    group by JPP_OH_Idnr, OH_Name
    having max(JPP_Lnr) > 255
    Currently, we have only a handful of such workflows. I think this number is not likely to increase dramatically in the near future.

    Tran-Hoang_Hau_348: I would still like answers to these questions:
    1. My understanding is that the DWP & AWI server need an extra 1-2 GB of memory onlymomentarily when handling large XML files or large workflows. Is this correct?
    2. What is a “huge” XML file?
    3. What is the maximum number of tasks allowed in a workflow?
    Thanks!


  • 11.  AE & AWI sizing

    Posted Mar 15, 2018 05:54 AM
    Hi Michael Lowry 
    Please find my respond on the below comment
    1.You are right, the memory will be required     momentarily when you have people working on the large xml file

    2.You can consider a maximum message size 30720 KB is huge one, since It's only the value that we allow, you can see this information on the link
    you can consider if 30MB XML than it could be few thousand of object inside, and if the AE need to proceed that kind of message then I believe it's not an easy time.

    3. I don't think that we have the limitation on the number of task within a workflow.

    Regards,
    Hau




  • 12.  AE & AWI sizing

    Posted Mar 15, 2018 08:07 AM

    Tran-Hoang_Hau_348: Thanks for your replies. About the maximum message size, I assume you are referring to XML imports. Is this maximum size due to a basic architectural limitation of the AE?

    In any event, largest XML file any of our users has exported to date is 15 MB in size. Most files are well under 5 MB in size. I suppose we will simply advise users to divide their batches into smaller units if the file sizes begin to approach 30 MB.



  • 13.  AE & AWI sizing

    Posted Mar 19, 2018 06:10 AM

    Hi Michael Lowry you were right I am referring to the link  due to the default value of AE system.



  • 14.  AE & AWI sizing

    Posted Mar 19, 2018 06:34 AM
    Thanks. I just submitted a new enhancement request, asking for an increase to the maximum size of XML imports.