Bug 573899 - Launching debug to remote server takes too much time
Summary: Launching debug to remote server takes too much time
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.19   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-01 16:02 EDT by Roman Bezugomonnov CLA
Modified: 2021-06-02 10:23 EDT (History)
1 user (show)

See Also:

Attachments
TCP dump (606.58 KB, application/octet-stream)
2021-06-01 16:02 EDT, Roman Bezugomonnov CLA 		no flags Details
Debug view (65.92 KB, image/png)
2021-06-01 16:04 EDT, Roman Bezugomonnov CLA 		no flags Details
Debug configuration view (88.54 KB, image/png)
2021-06-01 16:04 EDT, Roman Bezugomonnov CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Bezugomonnov CLA 2021-06-01 16:02:08 EDT 
Created attachment 286496 [details]
TCP dump

Hello, I've faced with performance issue while trying to debug remote server using Eclipse.
When I run my debug configuration in Eclipse it takes about 4-5 minutes but in other IDE or even in JDB from console it takes less than 1 minute (20-30 sec).

I've gathered TCP dump from start launching debug until finish.
It can be found in attachment.
Based on dump, it seems that Eclipse tries to get a lot of Thread and Monitor information because there are a lot of small JDWP commands while launching ( to get thread statuses, to get thread groups and etc).

At the same time, all checkboxes in debug view are disabled - show monitors, show running threads, show system threads and so on.

Could you please check why eclipse send a lot of unnecessary JDWP commands?
Comment 1 Roman Bezugomonnov CLA 2021-06-01 16:04:26 EDT 
Created attachment 286497 [details]
Debug view
Comment 2 Roman Bezugomonnov CLA 2021-06-01 16:04:58 EDT 
Created attachment 286498 [details]
Debug configuration view
Comment 3 Andrey Loskutov CLA 2021-06-02 10:23:56 EDT 
(In reply to Roman Bezugomonnov from comment #0)
> Created attachment 286496 [details]
> TCP dump
> I've gathered TCP dump from start launching debug until finish.
> It can be found in attachment.

Could you please export it to some csv/text format, I don't have wireshark installed and don't want to mess up with this tool on my workstation.

> Based on dump, it seems that Eclipse tries to get a lot of Thread and
> Monitor information because there are a lot of small JDWP commands while
> launching ( to get thread statuses, to get thread groups and etc).
> 
> At the same time, all checkboxes in debug view are disabled - show monitors,
> show running threads, show system threads and so on.
> 
> Could you please check why eclipse send a lot of unnecessary JDWP commands?

Roman, just guessing: do you have any (many?) breakpoints created, so might be that affects startup time?

Beside this, you might be affected by extra communication due too many threads on remote side / thread name change listener we have in the debugger. Try to start Eclipse with -Dorg.eclipse.jdt.internal.debug.core.model.ThreadNameChangeListener.disable system property.