Topic
6 replies Latest Post - ‏2013-12-09T10:22:03Z by kimbert@uk.ibm.com
SX14_Rahul_Singh
SX14_Rahul_Singh
14 Posts
ACCEPTED ANSWER

Pinned topic Execution groups

‏2012-10-11T19:05:59Z |
Based on my initial understanding of execution groups , for every execution group we have section of memory allocated by the operating system. I am trying to understand as to when does the need arise for us to create multiple execution groups and what are benefits of creating multiple execution groups. Do we have a restriction on the number of instances of message flows which can be run in a execution group?
Updated on 2012-10-16T18:26:45Z at 2012-10-16T18:26:45Z by SX14_Rahul_Singh
  • kimbert@uk.ibm.com
    kimbert@uk.ibm.com
    508 Posts
    ACCEPTED ANSWER

    Re: Execution groups

    ‏2012-10-11T22:52:44Z  in response to SX14_Rahul_Singh
    An execution group is a process. A message flow is a thread. There are no limits ( apart from the obvious hardware and software constraints ) to the number of flows in an execution group, or to the number of parallel instances of a flow. A WMB developer tunes these parameters to achieve the design goals for the system.

    Specifically, it will depend on the number of message flows, the type of operations that they are performing, the SLAs that you need to achieve, the characteristics of your chosen hardware and OS...I could go on.

    For reference, there are deployments of WMB that are running dozens of execution groups containing thousands of message flows, with some message flows having multiple instances. Scalability is a strong point of WMB.
  • Kalicharan
    Kalicharan
    49 Posts
    ACCEPTED ANSWER

    Re: Execution groups

    ‏2012-10-12T16:48:27Z  in response to SX14_Rahul_Singh
    "Number of flows in an EG" or "Number of EGs in a broker" are crucial for functioning of the broker and there are many factors that influence this decision

    1. Throughput of the flow
    2. Response time of the flow
    3. How process intensive the msgflow is
    4. RAM / Processing Speed on the server

    The more process intensive a flow is then it is better to keep it up in a separate EG. For medium sized company, we have like 15 EGs in a broker running on a windows server. But we do have separate EGs to distinguish various business areas. Also different Brokers for realtime services and batch services.

    There is no hard and fast rule or a standard practice. You have to take genuine decision based on the various factors that influence
    • fjb_saper
      fjb_saper
      120 Posts
      ACCEPTED ANSWER

      Re: Execution groups

      ‏2012-10-14T03:51:20Z  in response to Kalicharan
      Also keep in mind that if you define too many execution groups, the processor spends more time trying to allocate work to an e.g. than doing any work in the e.g.
      Not the desired outcome...

      Hard and fast rule of thumb: no more than 2 e.g. per processor allocated to the broker...
  • SX14_Rahul_Singh
    SX14_Rahul_Singh
    14 Posts
    ACCEPTED ANSWER

    Re: Execution groups

    ‏2012-10-16T18:26:45Z  in response to SX14_Rahul_Singh
    Thank you all so much for the response :)
  • Miyer.Buitrago
    Miyer.Buitrago
    1 Post
    ACCEPTED ANSWER

    Re: Execution groups

    ‏2013-12-06T04:52:40Z  in response to SX14_Rahul_Singh

    I have a Customer with more than 90 message flows in severals EG and currently we have problems with the performance, anyone knows of any document for this type of analysis with recommendations. Thank in advance

    • kimbert@uk.ibm.com
      kimbert@uk.ibm.com
      508 Posts
      ACCEPTED ANSWER

      Re: Execution groups

      ‏2013-12-09T10:22:03Z  in response to Miyer.Buitrago

      Probably best to open a new thread for this question, rather than appending to an existing thread.

      There are many articles about WMB performance tuning. If you give some details about the message flows and what type of performance problems you are experiencing then we should be able to point you in the right direction.