Jérôme Vervier

When selecting an asset in the asset tree, we've got three time consuming elements : 1. time consumption between or-asset-tree:_onNodeClicked and first or-mwc-input:updated (meaning first input builded in asset view...

Hi, In my research I found a time consuming step on Websocket side. When clicking on an asset in the asset tree, there is message exchante on WS linked to...

After some research, it seems the delay come after the call on org.openremote.manager.event.ClientEventService#sendToSession.

From my tests, time consumption is after the camel processing of sending back from the backend on the WS the message. Do not know why, for the moment, there is...

Hello @DonWillems, @richturner , I notice we're getting the asset info (attributes,...) about the asset we select in the asset tree with the response of the REQUESTRESPONSE message. For a...

ALso need to take a look on the TRIGGERED: message emit on the WS by the backend and their impact on frontend

Taking the issue by the other side (starting from event.ts file), I spotted the time consumption in https://github.com/openremote/openremote/blob/master/ui/component/core/src/asset-mixin.ts#L103 Those two await are consuming time AND blocking the handling of SUBSCRIBED...

Other finding (and why I didn't had that idea before!). I do not have the same response time to load asset page between chrome and other browsers (Firefox and Safari)....

This issue is not complete :-/ Improvement has been done on asset tree to improve the load/construction time. But We're still having an issue with Chrome based browser where the...

Considering to remove the Cancel button? And rename Apply button to OK