https://community.appian.com/discussions/f/best-practices/34267/slow-smart-servicesAfter i generate health check report they mention slow smart services (Text doc from template) Description :30435 calls, 10300 ms peak average, 100% chained In this smart service we call one expression to pass data to that template that expressionen-USTelligent Community 12https://community.appian.com/thread/130718?ContentTypeID=1Wed, 06 Mar 2024 11:14:16 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:28a68517-1d6f-486b-885a-44cbfc3fce9ekishorej1999<p><span>Hii purnavenkatasatyavaraprasadt0001<br />,<br /><br /></span><span>If this base64 decoding operation is performed frequently within the smart service (as indicated by the 30435 calls), it could contribute to the overall slowness of the service.&nbsp;The mention of &quot;100% chained&quot; suggests that the smart service calls might be chained, meaning that one service call is dependent on the completion of another. If the base64 decoding operation is part of this chain, it could further exacerbate the performance issue.<br /><br />If the chaining of smart service calls is causing performance bottlenecks, try to minimize dependencies between services or optimize the order in which they are called.&nbsp;If the input base64 strings are excessively large, consider limiting their size or finding alternative ways to handle them, such as streaming or chunking.<br /></span></p><div style="clear:both;"></div>