I have recently upgraded to v9.1.1.0 then to 9.1.2.0. With both versions I have noticed that when I launch the 32 bit version it loads in 7 seconds. On the same computer it takes over 30 seconds to launch the 64 bit version. When I launch the 64 bit version the RemoteDesktopManager64.exe process sits at 17% cpu util during the entire 30 seconds. The rest of the system is completely idle. Once it loads cpu util drops to 0%. The program operates normally after it loads, it just has a very annoying delay waiting for it to load.
Even at 7 seconds the 32 bit version launches slowly. All office apps (word, excel, powerpoint, visio, etc) each load in under 1 second. Even Photoshop loads in under 2 seconds on my system.
Is this slow load time for RDM normal? Do other users experience the same behavior?
I am running Windows 7 Professional 64bit service pack 1 with AMD Phenom II X6 1055T proc, 12 GB of RAM, and an Intel SSD.
Hi,
Unfortunately it's a known issue and we still recommend to use the 32 bit version if you don't reach the memory limitation. The real question is why.
The short answer is that 64 bit application consumes more memory (if you have an array of 64 bit pointers it will be larger than array of the same size with 32 bit pointers) More memory means that the garbage collection will work harder.
http://blogs.msdn.com/rmbyers/archive/2009/06/08/anycpu-exes-are-usually-more-trouble-then-they-re-worth.aspx
http://blogs.msdn.com/ricom/archive/2009/06/10/visual-studio-why-is-there-no-64-bit-version.aspx
David Hervieux
All other 64 bit apps I use don't have this problem, including 64 bit MS Office and Adobe CS to name just a couple. And I use a lot of 64 bit apps. The only app I have that launches horribly slow is Devolutions RDM. So it's a known issue. Hopefully you guys will get it fixed at some point.
Thanks for the feedback.
Those applications don't use the .NET Framework. That's the main problem. We will do our best to improve the 64 bit version but except if you reach the 32 bit memory limitation, you should continue with it. There is many technologies that just don't work in 64 bit.
David Hervieux
We now have a blog about this:
http://blog.devolutions.net/2014/02/32-bit-vs-64-bit-versions-of-remote.html
David Hervieux
Hi David
I don't see this as only as 32 v 64 bit issue, its a problem in general, let me give an example.
I have a well spec'd system (Windows 8.1 with i7, 32GB RAM and SSD), yet RDM still takes 25-30 seconds to start up. Its about 15 seconds before I even see the interface, then it takes another 10-15 seconds sitting at "Loading sessions from data source Local Data Source".
I can understand .NET runs slower than native applications, but why is taking 10-15 seconds to read a local data file that store the login details for about 20-30 RDP sessions? This needs some serious attention or redevelopment of the core code.
It has gotten so bad, I'm now actively looking for an alternative product :(
edited by kelv1n on 2/26/2014
Hi kelv1n,
Few question to help me:
1. What RDM version do you use?
2. What data source type do you use
3. Have you enabled the Intelligent cache?
David Hervieux
@kelv1n
Could you please send us a profile trace of the startup & full refresh for analysis along with your data source information.
- start RDM using /Profiler
- once loaded CTRL+refresh (icon)
- click "Send trace to" button
- mention this thread and my name in the subject
- File -> My Data Source Information
- click the mail icon, and send us your information
I will have a look at the numbers to see if there is anything in particular that might be slowing it down.
Regards,
Stéfane Lavergne
All,
I was able to somewhat reproduce the start-up "slowness" on a small machine running Windows 7. With that I was able to run some test and try out a few things. Good news is I think I have a solution.
Attached are two files (.exe & .bat) copy both files to your install directory & run the install.bat file. This will ngen all .dll & .exe files. It will take a few minutes so please be patient. A few of the files will fail it's not a big deal you can ignore the errors.
- close RDM
- copy files
- run install.bat - elevated command prompt, if do not worry the batch will prompt you :-)
- start RDM
Please let me know if it improves performance for you you.
Regards,
Oops can't upload .exe files, I've renamed it "ngen.exe.remove.this.txt"
edited by stefane on 2/27/2014
updated the install.bat file
edited by stefane on 3/3/2014
Stéfane Lavergne
install.bat
ngen.exe.remove.this.txt
uninstall.bat
Thanks Stefane.
Startup time is still around 20-25 seconds, I've include the profile
LoadConnections [Xml : Connections]...
LoadConnectionsFromDataSource...
LoadDataSourceSettingsFromDataSource...
GetDataSourceSettings : 1 ms
LoadDataSourceSettingsFromDataSource : 7 ms
GetConnections...
Xml.GetConnections...
Xml.GetConnections : 3696 ms
GetConnections : 3703 ms
DoSetConnections...
DoSetConnections : 64 ms
LoadConnectionsFromDataSource : 3822 ms
LoadConnections [Xml : Connections] : 5793 ms
TreeView.LoadConnectionList...
GetGroupInfos : 1 ms
BeginUpdate...
ApplyGroupCustomImages : 0 ms
LoadConnectionInTreeNode : 36 ms
PreCreateGroups : 13 ms - Count : 1
BeginUpdate : 48 ms
TreeView.LoadConnectionList : 114 ms
LoadTrayiconContextMenu : 7 ms
LoadConnections [Xml : Connections]...
LoadConnectionsFromDataSource...
LoadDataSourceSettingsFromDataSource...
GetDataSourceSettings : 0 ms
LoadDataSourceSettingsFromDataSource : 5 ms
GetConnections...
Xml.GetConnections...
Xml.GetConnections : 27 ms
GetConnections : 36 ms
DoSetConnections...
DoSetConnections : 1 ms
LoadConnectionsFromDataSource : 71 ms
LoadConnections [Xml : Connections] : 90 ms
TreeView.LoadConnectionList...
GetGroupInfos : 0 ms
BeginUpdate...
ApplyGroupCustomImages : 0 ms
LoadConnectionInTreeNode : 7 ms
PreCreateGroups : 0 ms - Count : 1
BeginUpdate : 19 ms
TreeView.LoadConnectionList : 41 ms
edited by kelv1n on 2/27/2014
@kelv1n
Are you running RemoteDesktopManager.exe or RemoteDesktopManager64.exe?
Make sure you use RemoteDesktopManager.exe. Does it change anything?
The install.bat file created a log file called ngen.log or ngen.txt could you please post the file for me.
Regards,
Stéfane Lavergne
@kelv1n - please try with the following (updated) script
Make sure you run uninstall.bat then run the new install.bat script.
Best regards,
edited by stefane on 3/3/2014
Stéfane Lavergne
install[1].bat
Thank Stefane, I gave it a try and did not see any noticeable improvement. Perhaps its just my system. For now I'm just using a different tool, I'll try again next time I re-install my laptop.