speed up chrome webpage initial connection
0 vote
Ok ok, I know RDM uses a 3rd party chrome .NET from essential objects. No need to rehash.
However, with the upcoming conversion of Edge over to Chromium this is related to my previous question about long term plans for web entries.
https://forum.devolutions.net/messages.aspx?TopicID=32876
However, this is a direct feature request. Is there a way to PLEASE speed up the time it takes for RDM to actually launch a chrome web entry? if I double-click a chrome entry, it takes at least 5-8 seconds to even launch the website initially. In the mean time there is a status bar that is displayed that says 'launching web page' or something to that effect.
Why does it take 5-8 seconds just to launch that web page initially? And it's not just launching chrome initially... it takes 5-8 seconds to launch ANY chrome entry. Even if I just launched a separate chrome entry, and I launch a different one.... that one will take 5-8 seconds to initially load too. Why?
Why is there not a way to have whatever RDM is doing in the background for those 5-8 seconds pre-loaded? So when I go to launch a chrome entry and launches within 1-2 seconds like RDP, SSH and other entries do?
All Comments (7)
Hello,
I already tried that with no success. I tried to open a web page in background but for an unknown reason it made no difference. My goal at that time was to replace our dashboard overview in IE with embedded Chrome but because of the performance, I had to postpone it.
Regards
David Hervieux
So what is the cause of this 5-8 seconds of delay? What exactly is happening the background that takes so long?
Has this delay been brought up to Essential Objects?
Yes it has but they have to start the Chrome engine. It's not like IE which is running in the background of Windows. We hope to be able to replace it with the new Edge Chromium engine.
Regards
David Hervieux
isn't the edge chromium going to have the same delay issues? That was kind of my point in my original thread linked above where I asked about the long term plans.
Or will the Edge Chromium have native .NET so you don't need to do the whole EO conversion of the browser into .NET
We can't be sure for now. We need to see the Microsoft Edge .Net Integration but I'm pretty sure that Edge will be running behind the scene which will make the warm up time nearly invisible. Anyway I will double check what we can do with EO.
Regards
David Hervieux
Do you have any ETA? The final beta for Chromium Edge was released Nov 4th. I think it goes full release this month. Have you guys been playing with the beta internally?
There is no .NET binding yet and unfortunately I can't give you an ETA.
David Hervieux