Question
DICTU RDI
NL
Last activity: 27 May 2025 5:15 EDT
Poor performing service: RULE-SERVICE-REST APPLICATION V2!ATTACHMENTS_UPLOAD
We are uploading documents in case, it is taking 12.81s to upload using the pega provided REST API So we wanted to understand why this service takes more time.
We are uploading documents in case, it is taking 12.81s to upload using the pega provided REST API So we wanted to understand why this service takes more time. 2025-04-14 11:00:29,321 GMT*8*PEGA0011*12809*1000*at-dev01pega-as-8-gggn5*NA*NA* A782F9XU4TV5EUFIQ1USZ99CUYA7F3JZEA*[email protected]*OCS-EMW-Work* EMW:01.01.13*b2bc9dac43245389cf13a3d90fc6e722*Y*472*HDU25RJ607K12A4FKRVAKDU62CXCWQ7S6A* 1452*http-nio-8080-exec-11*STANDARD*com.pega.pegarules.integration.engine.internal. services.ServiceAPI*pega-as-8-gggn5| Proprietary information hidden|Rest|application|v2| attachments_upload79671466aeeacbfc71e92320776c55b0|A782F9XU4TV5EUFIQ1USZ99CUYA7F3JZEA* ServicePAL.Rest.application.v2.attachments_upload79671466aeeacbfc71e92320776c55b0* Rule-Declare-Expressions*CODE-PEGA-LIST PZLOADPARAMETERSFORRULE #20190724T221841.887 GMT Step: 5 Circum: 0*NA*true*POST-attachments-11-00-16-548-A782F9XU4TV5EUFIQ1USZ99CUYA7F3JZEA* **pxRunModelCount=38;pxDeclarativePageLoadElapsed=1,26;pxRulesExecuted=298;pxJavaGenerateCount=4;pxJavaGenerateElapsed=1,00;pxDBInputBytes=1.539.124;pxAlertCount=2;pxDeclarativeRulesLookupCount=231;pxInputBytes=29;pxDeclarativeRulesInvokedElapsed=0,01;pxRuleIOElapsed=0,07;pxServiceCount=1;pxDeclarativePageLoadCount=7;pxJavaAssembleHLElapsed=1,58;pxDeclarativeRulesLookupElapsed=0,03;pxProceduralRuleReadCount=73;pxRuleFromCacheCount=44;pxDBOutputBytes=3.080;pxRDBRowWithoutStreamCount=19;pxServiceDataVolume=29;pxJavaCompileCount=11;pxCommitRowCount=1;pxRDBIOElapsed=0,03;pxDeclExprCtxFreeUseCount=22;pxRDBIOCount=39;pxJavaAssembleCount=11;pxServiceActivityElapsed=9,59;pxTotalReqCPU=1,34;pxRunWhenCount=172;pxBytesAllocated=193.735.016,00;pxOtherCount=1.484;pxTotalReqTime=12,81;pxActivityCount=44;pxOtherFromCacheCount=1.101;pxRDBWithoutStreamCount=19;pxRunOtherRuleCount=4;pxJavaAssembleElapsed=0,06;pxCommitCount=1;pxDeclarativeRulesInvokedCount=26;pxInteractions=1;pxRuleCount=66;pxServiceOutMapReqElapsed=0,00;pxJavaCompileElapsed=0,42;pxRulesUsed=305;pxOtherIOElapsed=0,29;pxCommitElapsed=0,01;pxTrackedPropertyChangesCount=16;pxDeclarativeRuleReadCount=1;pxDeclarativeNtwksBuildHLElapsed=0,04;pxOtherIOCount=435;pxDeclarativeNtwksBuildConstElapsed=0,01;*NA*NA*NA*NA*NA*NA*RULE-SERVICE-REST APPLICATION V2!ATTACHMENTS_UPLOAD79671466AEEACBFC71E92320776C55B0 #20241007T072446.840 GMT has exceeded the threshold of 1.000 ms: 12.809 ms;pxServiceInMapReqElapsed=0;pxServiceOutMapReqElapsed=2;pxServiceActivityElapsed=9591;pxParseRuleTimeElapsed=0;ServiceURL=https://at-dev01.rijkszaak.rijksweb.nl/prweb/app/energy-meter-wissel-1/api/application/v2/attachments/upload;*
***Edited by Moderator Marije to add INC-C22189s***
HCA Healthcare
US
The poor performance of the RULE-SERVICE-REST APPLICATION V2!ATTACHMENTS_UPLOAD REST service, taking 12.81 seconds to upload a document, is mainly due to the service activity itself (pxServiceActivityElapsed=9.59s) consuming most of the time. This indicates that the internal logic, likely the activity processing the file upload, is doing too much—possibly including file processing, data mapping, or saving large attachments. Additionally, metrics show high rule execution (pxRulesExecuted=298), Java compilation, and declarative rule activity, which means complex or inefficient logic may be triggered during upload. To fix this, review and optimize the service activity—break it into smaller reusable parts, reduce rule calls, and use asynchronous processing if immediate response isn’t critical. Also, check if the file size is too large and enable compression or chunked uploads if supported.
Would you like help analyzing the service activity steps or logs in more detail?
DICTU RDI
NL
@Sairohith Yes i need more help. i also raised support ticket.