I tried to updated with the latest version but still getting this logs in Service Center > Monitoring > GeneralDoes this exist on your end as well? Is this expected?TIA..
Hi Jester,
Seems like a sleep action, that waits a few seconds intentionally. Because of the wait, OutSystems considers this a slow extension.
It is just a warning and probably in this case a false positive.
You can open the extension code in Microsoft visual studio and inspect the code to figure out why there is a sleep period build in.
Regards,
Daniel
The "SlowExtension" warning is indeed because of the Thread Sleep usage like Daniël mentioned.
This is required to periodically ping the client - a HeartBeat event - to check if said client is still alive while keeping the SSE protocol open.
The ping frequency can be adjusted at the SSE_IS Module Site Property "HeartBeatTimer".
I usually have it higher than the default 10 seconds - 300, 600 seconds or even higher. This will reduce the warning frequency.
Other than that, I currently don't have anything thought out to circumvent that warning.
Hi,
is there any known impact of this action on the server resources?
kind regards
Wouter
Hi Wouter,
- the latest SSE HUB versions will only emit this log when a client disconnects for the reasons above
- each connected client is just a REST call. The impact on the server is just that of n clients concurrently connected to your server. Theoretically there is no limit, and the resource consumption on IIS of a single REST call is negligible - however, having 100 customers or 1Million connected to a single Server has an impact. The best way to check is to check your Front End Server capacity regarding concurrent REST API calls with OutSystems, and scale if appropriate.
- finally, SSE is a lightweight signal mechanism, it is meant to signal that something changed or data is available on the server. Using it to send the data itself puts strain on the server that is behind the scope of the component.
Nuno