3 comments
Comment actions Permalink

Hello Eugene,

More details: after the file is parsed (green square) everything runs
smooth, but opening a file (e.g. from Find usages) and typing until it
is parsed seems "viscid".

Tom


On Wed, 2 Oct 2002 16:11:55 +0200, "Eugene Belyaev" <beg@intellij.com>
wrote:

Tom,

The only case where we have found out that typing slows down is when the
line you are working with becomes (or is) the longest line in the file.
Please check if this is the case.

Eugene

"Thomas Singer" <idea@regnis.de> wrote in message
news:3d9acff9.13231475@news.intellij.net...

Hello Eugene,

>

From a subjective point of view, build 651 is slower than previous
builds. We only do plain Java development (no J2EE stuff) and have
fairly small classes (~200..300 lines per file). But editing seems
"viscid". Normal keystrokes require ~1/2 second (guessed) to be
processed. Ok, 1/2 second sounds not much, but compared to previous
builds or native applications it is very much.

>

Tom

>
>

On Tue, 1 Oct 2002 21:35:51 +0200, "Eugene Belyaev" <beg@intellij.com>
wrote:

>

Hi,

>

In #651 we have fixed a number of performance issues, so please check it

and

report asap.

>

Thanks,
Eugene Belyaev

>
>

>


0
Comment actions Permalink

There are still the same performance problems in build 657: the first
seconds after opening a file (ca. 5 seconds for a 300 lines Java file)
you cannot edit the file because of the significant slow down.

Tom


On Fri, 04 Oct 2002 14:45:56 GMT, idea@regnis.de (Thomas Singer)
wrote:

Hello Eugene,

More details: after the file is parsed (green square) everything runs
smooth, but opening a file (e.g. from Find usages) and typing until it
is parsed seems "viscid".

Tom


On Wed, 2 Oct 2002 16:11:55 +0200, "Eugene Belyaev" <beg@intellij.com>
wrote:

Tom,

The only case where we have found out that typing slows down is when the
line you are working with becomes (or is) the longest line in the file.
Please check if this is the case.

Eugene

"Thomas Singer" <idea@regnis.de> wrote in message
news:3d9acff9.13231475@news.intellij.net...

Hello Eugene,

>

From a subjective point of view, build 651 is slower than previous
builds. We only do plain Java development (no J2EE stuff) and have
fairly small classes (~200..300 lines per file). But editing seems
"viscid". Normal keystrokes require ~1/2 second (guessed) to be
processed. Ok, 1/2 second sounds not much, but compared to previous
builds or native applications it is very much.

>

Tom

>
>

On Tue, 1 Oct 2002 21:35:51 +0200, "Eugene Belyaev" <beg@intellij.com>
wrote:

>

Hi,

>

In #651 we have fixed a number of performance issues, so please check it

and

report asap.

>

Thanks,
Eugene Belyaev

>
>

>


0
Comment actions Permalink


Yes I have found this problem too. This is currently the major draw back,
and it would be nice if they look into this performance problem.


"Thomas Singer" <idea@regnis.de> wrote in message
news:3da57b1a.19387067@news.intellij.net...

There are still the same performance problems in build 657: the first
seconds after opening a file (ca. 5 seconds for a 300 lines Java file)
you cannot edit the file because of the significant slow down.

>

Tom





0

Please sign in to leave a comment.