[jbosstools-issues] [JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
André Dietisheim (Jira)
issues at jboss.org
Tue Aug 27 04:20:01 EDT 2019
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775455#comment-13775455 ]
André Dietisheim edited comment on JBIDE-26794 at 8/27/19 4:19 AM:
-------------------------------------------------------------------
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here.
On the other hand, remote debugging - I think - isn't the dominant usecase.
was (Author: adietish):
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here.
Compare yourself (done with the preference "Show method result after a step operation" turned off, thus the difference is not that extreme any more):
* Eclipse: https://youtu.be/MkebG9L5xBQ
* IntelliJ: https://youtu.be/tykb_xdjJEg
On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: debugging
> Fix For: 4.13.x
>
> Attachments: disable-show-method-result.png
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/workshop/lab/common-environment)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
More information about the jbosstools-issues
mailing list