Forum / Remote Desktop Manager - Bug Report

Slow Filter performance due of reload of all cons

  • Create an Issue
  • Cancel

We take high use of the filter option down left in RDM. Since ca few Versions the connections are reloaded several times whilt typing in filter conditions (to see in profiler). That causes very slow response of the filter. Perhaps it is possible not to relad the connections so often?

RDM 13.0.6.0
MS SQL 2016 DataSource
4450 Session entries

Clock6 yrs

You means that when you filter, you see in the profiler a reload? What type of data source do you use?

David Hervieux

signaturesignature

Clock6 yrs

Yes, we use a MS SQL 2008R2 Server DataSource.


Here is what profiles says during filtering. It does this everytime you add a new letter to the search-field, if you are typing too slow...


TreeView.LoadConnectionList...
Tree view is loading 1621 connections
GetGroupInfos : 0 ms
BeginUpdate...
Loading Group Kunden [03769c8d-ea04-4ba2-8ae6-a7242b4b2974]
Excluded connection: parent = null && IsExcluded
Loading Connection Dokumentation [783a075e-0f4c-42f5-9647-1a7d5847479a]
Excluded connection: parent = null && IsExcluded
Loading Connection A*****PDC [9d45663d-55a5-474f-beb1-ce9357a5e055]
Excluded connection: parent = null && IsExcluded
Loading Credential A***** [b18410a6-d974-418e-9466-d2bcfca8c647]
.
.
.
..
. snipped other sessions
.
..
.
Loading Connection S***** [2d834b79-95bf-4847-9166-1fd79b65ae82]
Excluded connection: parent = null && IsExcluded
Loading Connection S*****SQL1 [7819527e-2289-4061-a44d-127b0316bb05]
Excluded connection: parent = null && IsExcluded
Loading Connection S*****SRV1 [b0dad379-4f93-4a7d-b3d1-1ca70b0d6d8f]
Excluded connection: parent = null && IsExcluded
Loading Connection S*****SRV2 [4830477e-13ce-48bf-b3b6-b0f33ed6f2ab]
Excluded connection: parent = null && IsExcluded
ApplyGroupCustomImages : 0 ms
LoadConnectionInTreeNode : 21689 ms
PreCreateGroups : 0 ms
BeginUpdate : 11 ms
TreeView.LoadConnectionList : 21723 ms

RDM 13.0.6.0
MS SQL 2016 DataSource
4450 Session entries

Clock6 yrs

Set your debug level down to 0 (zero) and try again.

It is taking 21+ seconds to load, must of that time is writing debug logs. With the profiler window open and debug level 0 the debug impact will be at a minimum.

Regards,

Stefane Lavergne

signaturesignature

Clock6 yrs