[progress Communities] [progress Openedge Abl] Forum Post: Re: Corticon Process Duration Time

[Chris S. Hogan]

Here is a detailed breakdown of two ways you can get timing information back for decision execution times: ############################################################################################################### # Specifies whether the Server Execution start and stop times are appended to the CorticonResponse document # after ICcServer.execute(String) or ICcServer.execute(Document) is performed. # # Default value is false ############################################################################################################### com.corticon.ccserver.appendservertimes= false *** The description for this property only states that the execution start and stop times will be appended. This description is pretty outdated. Many more metrics will be added to the CorticonResponse than just those two numbers. Now, by setting this property to “true” on the CcServer, this means that every execution will append the execution values to the CorticonResponse. Just in case the customer doesn’t want all this information in every CorticonResponse, you can set an Attribute in the CorticonRequest to append the execution times for just that execution while keeping the above property set to “false”. You do have that option. Here is an example of what is returned in the CorticonResponse when the flag is set to true or the addTimes=”true”: *** A little overwhelming…I know . Here is maybe a better look at how things are broken down: ccExeStart :: ccExeStop =Total Execution ccPreprocessPayloadStart :: ccPreprocessPayloadStop =Preprocess Payload ccReactorWaitStart :: ccReactorWaitStop = Reactor Wait ccExecutionWaitStart :: ccExecutionWaitStop = Execution Wait ccExecutionProcessStart :: ccExecutionProcessStop = Core Rule Processing ccExecutionPreprocessStart :: ccExecutionPreprocessStop = Preprocess Execution ccExecutionTranslationStart :: ccExecutionTranslationStop = Payload to CDO ccExecutionRulesStart :: ccExecutionRulesStop = Rule Execution ccExecutionRulesPostProcessStart :: ccExecutionRulesPostProcessStop = Post Process Execution I do not breakdown the buckets in RED …I actually thought that would be too much detail. Round Trip Execution Transmission Total Execution Preprocess Payload Reactor Wait Execution Wait Core Rule Processing Preprocess Execution Payload to CDO Rule Execution Post Process Execution Logger EDC (EntityManager) EDC (commit/rollback) Add RuleMessages to Response Record Metrics Christopher S. Hogan Principal Systems Engineer office 346-352-0699 mobile 646-243-4282 www.progress.com

Continue reading...