1. In case of multi node clustered environment, is it required to run for each node or cluster? I see there is a property that we set in the prstaticassembly.properties file to specify the no. of JVMs. What is there relevance of that? If the assembled rules gets stored into DB then running it only once should serve the purpose , please confirm if my understanding is correct.  

   
   

   1. >>> that is correct! since results are stored in the db, dont have to execute for each jvm.

2. Does static assembly process only update DB or it also update the disk?

   
   

   1. >>> its only the db.

3. PRPC 7.1.X the “Static Assembler” is available for the user to kick off himself at (Pega button) > System > Tools > Static Assembler. Does that mean after new code deployment running this from one of the node is what required to pre-assemble all the rules?

   
   

   1. >>> it depends on no of rules being introduced in the release. for incremental releases, most likely you dont need them. probably you may want to validate it in one of the envs like QA/Test to determine the benefit. 

4. How to verify that all the required assemble is done and the end user is benefited from this.

   
   

   1. >>> after the static assembler execution, if users start using the application, there should not be any additional updates to 'pr_assembledclasses' table, since rules should be assembled already.

5. Is there a way to not to include based on application each time when we do static assembly ?

   
   

   1. >>> this could be a product enhancement, if you could show the evidence & benefits.

6. In the log snapshot there are entries as below, what is the reason of this and do we care about this?

   
   

   1. No of Rules Not Assembled : 400

   2. No of Rules Not Eligible : 1404

      
      

      1. >>> looks like an information only. while verifying assembly results, if you notice additional updates to 'pr_assembledclasses' table, then this numbers needs to be revisited.

Thanks Gopi and Celeste for providing these useful info. This will help planning this utility to execute in production environment.

I have now below additional questions,

1. I was thinking to run this utility each  time there is a release deployment with a good amount of new/modified features going to production and hence will have a better User Experience (performance wise) on the next day. That is the reason of asking why the "based on" application is required to assembled every time. Please suggest when and how often we should run this utility to get the maximum benefit.

2.  In the log snapshot there are entries as below, what is the reason of this and do we care about this?

1. No of Rules Not Assembled : 400

2. No of Rules Not Eligible : 1404

Is it really informational ? In the log there are exceptions ( exactly 400) for each rules that are not assembled. I am attaching the log for your reference. Please confirm if we shouldn't worry about these.

few more question:

1. In PRPC 7.1.X the “Static Assembler” is available for the user to kick off himself at (Pega button) > System > Tools > Static Assembler. Is it exactly the same as running the above utility from application server as standalone/ utility mode.

2. If both process are same , why it was suggested to run the utility while the application is stopped but in case of (Pega button) > System > Tools > Static Assembler it is only possible to run when the application is running.