host of issues with RDM 14

Hello Hazen,

This is an impressive topic and we would need some time to test and validate everything mentioned above.

I will assign this thread to one of our service desk agent as well as our QA department so that they can have a look at all of this together.

We will keep you inform regarding all your points.

Best regards,

Thanks Jeff. I'd also like to mention that my issues in no way imply that I don't love RDM. It's amazing and a game changer for me and my team in terms of productivity. These are all minor (through sometimes quite annoying) little issues/bugs. Nothing show stopping.

Hello Hazen,

Sorry for the delay and thank you for your patience.

You will find below my answers to your different points. Unfortunately, you will notice that most of my reply request a video. The reason for this is that I am aware that you performed a lot of changes to your UI that might prevent me from replicating the exact same behavior.

1- RDM need to first have the focus in order for the double click to work. This may be the reason why you mainly experience this issue the first time you open RDM.

2 ,3, 4, 6, 7 -Would it be possible for you to provide me a recording of these behaviors? This would provide me a better understanding of this issue.
Please use the following sharefile link in order to send us these videos https://devolutions.sharefile.com/share/getinfo/raba75bde4424504b.

5- Would it be possible for you to point me toward the forum topic in question?

Thank you for your collaboration.

Best regards,

So your internal screen capture thing doesn't capture split screen and other items. It also breaks the focus of the application so I had to use my cell phone. Sorry for the large video sizes. But I have uploaded all the issues. The file names correspond to the issue that the video is addressing.

As far as issues 1 and 3, I have narrowed those down the fact that I do not display the 'dashboard' tab in my layout. If I have the dashboard as an option then I don't encounter issues 1 and 3. But if I change my layout to not include the dashboard issues 1 and 3 happen every single time.

For issue 5
original thread : https://forum.devolutions.net/topic30553-chrome-and-firefox-slowness-embedded-mode-after-installing-windows--.aspx

also, something else you can see from some of the videos is how long RDM takes to open! Over 14 seconds in some cases. It is installed on an NVMe SSD with win10 latest patches.
On a GigE connection to the SQL database with less than 40ms latency to the database. 14+ seconds!!!

Hello,


Thank you for your video, I will see what can be done about these and I will contact you again if we require more information.


For the issue reported on the following forum topic https://forum.devolutions.net/topic30553-chrome-and-firefox-slowness-embedded-mode-after-installing-windows--.aspx
please make sure that "Disable RUNDLL32.exe" is still enabled. The issue reported in this thread has been fixed in the version 14.0.4.0 of RDM.


Regarding the slowness issue you are experiencing, could you please try the followings and see if the issue persist:


Disable the Splash Screen:File -> Options -> General -> Application Start and uncheck Show Splash screen
[/ol]
Could you please go to your Remote Desktop Manager installation folder, locate a file called “OptimizeRDM.bat” and run it as an Administrator.
[/ol]
If the issue still persist, would it be possible for you to run the “Profiler” and send it to us? The “Profiler level” will need to be set to “0”
For more information on that matter, please refer to the following help topic https://help.remotedesktopmanager.com/help_profiler.htm


Best regards,

splash screen is already disabled.
ran the optimizer. several errors. see attached.
after running, RDM seems marginally faster loading, but maybe by only 1 or 2 seconds. Still very slow.


I'm also not sure how I'm going to run the profiler since you need to have RDM already open to run it. How am I going to troubleshoot slow startup with the profiler?

Hello,

Thank you for this information.

The Profiler can be launched at startup using the "/Profiler" Command Line Arguments. To do so, perform a Win + R, locate your "RemoteDesktopManager64.exe" file then type "/Profiler". Doing so will launch Remote Desktop Manager with the profiler running in the background.

I will need to see the content of this log, would it be possible for you to send it to support@devolutions.net?

For more information on that matter, please refer to the following link:
https://help.remotedesktopmanager.com/index.html?installation_commandlinearguments.htm

Best regards,

Could you try to open the application with an empty Xml data source? I want to see if it's the initial data source connection is slowing down the opening of the application.

Regards

profilers attached. I can't set the profiler to 0 via command line so it defaulted to level 1

either way, they are attached.

@David, I will say this. It definitely is the SQL datasource. Loading a blank xml data source RDM opens and is ready to use in about 2-3 seconds.
So if it is indeed the SQL datasource, what do we need to do about it?

Also, as another test. Here is a profiler set to level 127 with RDM already opened on a blank XML and me actually 'switching' to my SQL datasource once RDM is already open.

This is the latest from our database team about RDM slowness and us having narrowed it down to the SQL datastore.

Hello,
RDM is using the default .NET pooling but your slowness is at the startup and we need to establish the initial connection.

Regards

It's not just during the startup. Yes, startup is incredibly slow. But interacting with RDM when needing to make database calls like 'refreshing' the datastore, rightclicking and going to the properties of an entry, etc, are all things that are also slow and takes 2-5 seconds.

How many entry do you have in your repository?

Regards

1980

Any updates on any of these issues?
The slowness of opening RDM and trying to do basic administration like editing properties of entries, etc seems entirely related to our SQL datastore and the latency involved.
We are working to move the database to a closer geographical datacenter.

Other than that, still hoping that the other items I've brought up in this thread are being worked on.

Hello,
I did a small fix for the first time double click. It seems to work fine on my computer.

As you can see from your profiler logs, reading the connections on a "full reload" takes 18+ seconds. So moving your database to a closer data center will help reduce network latency issues:
11:08:20.122536 Database.GetConnections...
11:08:38.994615 Reading connections from database : 18879 ms
11:08:39.010071 DecryptData : 5 ms - Count : 1852
11:08:39.322515 DeserializeData : 312 ms - Count : 1852
11:08:39.322515 Database.GetConnections : 19319 msArticles like the following could also be helpful in diagnosing your SQL Server install.
https://www.red-gate.com/simple-talk/sql/performance/a-performance-troubleshooting-methodology-for-sql-server/

As for the slowness on right-click > Properties, you can disable File > Options > Advanced > "Force refresh before edit entry". This is a work around to the fact the your SQL Server is slow, it won't perform a refresh before editing the session. I recommend you re-enable this after you've moved your SQL Server.

Best regards,

I definitely want to move our SQL database closer, but I don't understand why it would take 18 seconds to load the connections when the database is only about 80-100ms away 'network wise'.
But we will circle back once we move the datastore to a datacenter that is closer to our office.

I concur it is very odd.

Figuring out what is actually slowing you down is not trivial but SQL Server has a few quick options/tools that might help.

Could you please execute the following, in SSMS (SQL Server Management Studio). Please include "Client Statistics" Shift+Alt+S and run it a few times. Now look at the "Client Statistics" tab. That stat you want to look at is "Total execution time", it is in ms. Please post a print screen of the output.

declare @Version binary(8) = 0x0000000000000000;
declare @VersionDeleted binary(8) = 0xFFFFFFFFFFFFFFFF;
declare @DefaultRepositoryID uniqueidentifier = '00000000-0000-0000-0000-000000000000';
declare @RepositoryExistsID uniqueidentifier = '00000000-0000-0000-0000-000000000000';
declare @RepositoryID uniqueidentifier = '00000000-0000-0000-0000-000000000000';
declare @GlobalRepositoryID uniqueidentifier = '00000000-0000-0000-0000-000000910BA1';

select c.ID, c.Data, c.SecurityGroup , c.AttachmentCount, c.AttachmentPrivateCount, c.TodoOpenCount, c.HandbookCount
from dbo.Connections c where isnull(c.RepositoryID, @DefaultRepositoryID) in (@RepositoryID, @GlobalRepositoryID)
and c.Version > @Version;
select ch.ConnectionID as ID, ch.ConnectionType, ch.SecurityGroup, ch.GroupName
from dbo.ConnectionHistory ch
where ch.Version > @VersionDeleted and ((ch.HistoryType = 'D' and isnull(ch.RepositoryID, @DefaultRepositoryID) in (@RepositoryID, @GlobalRepositoryID)) or (ch.HistoryType = 'M' and isnull(ch.RepositoryID, @DefaultRepositoryID) not in (@RepositoryID, @GlobalRepositoryID)));
select max(Version), @@DBTS from (select max(c.Version) as Version from dbo.Connections c where isnull(RepositoryID, @DefaultRepositoryID) in (@RepositoryID, @GlobalRepositoryID)
union all
select max(c.Version) as Version from dbo.ConnectionHistory c where (isnull(RepositoryID, @DefaultRepositoryID) in (@RepositoryID, @GlobalRepositoryID) or (isnull(RepositoryID, @DefaultRepositoryID) <> @RepositoryID and HistoryType = 'M'))) a;select ID, Name, ImageBytes, ImageName, IsAllowedOffline, RepositorySettings from dbo.Repository where ID = @RepositoryExistsID;

Just checking in.

It seems issue 1 has been addressed based on the release notes for version 14.0.1.0. Can anyone confirm this fix addressed this specific issue?

Issue 2 is still present as of 14.0.9.0. The split screen boxes are still very tiny.

Issue 3 seems to have been addressed in some version as of 14.0.9.

Issue 4 is still present as of 14.0.9.0. If you close the left most session the right most session does not fill the whole screen.

Issues 5, 6, and 7 I am no longer experiencing.