Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Debugging - too slow (in some cases)(Too slow to reach first break point after large input strem)
Debugging - too slow (in some cases) [message #1716004] Mon, 30 November 2015 12:08 Go to next message
Martin Kalmancai is currently offline Martin KalmancaiFriend
Messages: 1
Registered: November 2015
Junior Member
Hi,

I'm using mars 4.5.1. and I'm having serious problem with debugging mode.

It's just taking enourmous time to reach first breakpoint.

I'm working with large input streams files around 600-1000mb (using buffered reader), whole post processing and reading together takes around 2 minutes, but when I select breakpoint after this section, it takes enourmous time.
I've waited for 45min without any results, so I've stopped it.

Any suggestion, why debug is so slow in this case ?

Thanks for any advice ! Smile

Re: Debugging - too slow (in some cases) [message #1726361 is a reply to message #1716004] Fri, 11 March 2016 19:41 Go to previous messageGo to next message
pepe potamo is currently offline pepe potamoFriend
Messages: 2
Registered: March 2016
Junior Member
I have a similar problem. If there are structures to inspect it can take more than 10 minutes to show the contents and can take more than one minute to execute an step. So if you need to step 10 times you'll spend 10 minutes.
I've tested with eclipse indigo, luna and mars. All of them the same. Always in ubuntu9.x, 10.x, 11.x, 14.x
Will it be fixed any year?
Re: Debugging - too slow (in some cases) [message #1726392 is a reply to message #1726361] Sat, 12 March 2016 09:45 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33142
Registered: July 2009
Senior Member
I've never seen that kind of behavior after using the debugger for more
than 10 years. A prerequisite for fixing a problem is typically being
able to reproduce the problem in the first place, so if no one ever
provides a way to reproduce the problem and the developers have no
theory that they might be able to use to reproduce it themselves, it's
highly unlikely that anything will be done (because it's impossible).

I.e., the title itself qualifies the problem with "in some cases", but
it doesn't illustrate the cases in a way that allows another developer
to reproduce it.


On 11.03.2016 20:41, pepe potamo wrote:
> I have a similar problem. If there are structures to inspect it can
> take more than 10 minutes to show the contents and can take more than
> one minute to execute an step. So if you need to step 10 times you'll
> spend 10 minutes.
> I've tested with eclipse indigo, luna and mars. All of them the same.
> Always in ubuntu9.x, 10.x, 11.x, 14.x
> Will it be fixed any year?


Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Debugging - too slow (in some cases) [message #1726399 is a reply to message #1716004] Sat, 12 March 2016 13:45 Go to previous message
Eclipse UserFriend
Not enough information to consider, but couple of general points

1) Debugging turns off the JIT so no speed ups by doing just in time compiling

2) Sometimes a limited data set can still product the same result (bug hit). might try using only part of the data.

3) find ways to optimize that section of code before debugging. it will be faster in debug and faster in actual use.

4) if data set gets buffered into structures in storage, are you running on large enough environment to avoid lots of swapping.

5) if using remote jvm connection for debug. try and move the eclipse and debug environment onto same machine to avoid costly network delays.


On 11/30/2015 3:13 PM, Martin Kalmancai wrote:
> Hi,
>
> I'm using mars 4.5.1. and I'm having serious problem with debugging mode.
>
> It's just taking enourmous time to reach first breakpoint.
>
> I'm working with large input streams files around 600-1000mb (using buffered reader), whole post processing and reading together takes around 2 minutes, but when I select breakpoint after this
> section, it takes enourmous time. I've waited for 45min without any results, so I've stopped it.
>
> Any suggestion, why debug is so slow in this case ?
>
> Thanks for any advice ! :)
>
>
Previous Topic:how to debug Java abstractorprocessor in plugin
Next Topic:Get some nulls when call node.resolveBinding()
Goto Forum:
  


Current Time: Fri Apr 26 16:29:03 GMT 2024

Powered by FUDForum. Page generated in 0.03963 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top