Slow response in Eclipse after upgrading to RTC 4.0.6

Anders Persson (1●2●2) | asked Apr 16 '14, 3:06 a.m.

After upgrading from RTC 4.0.1 to 4.0.6, our users complain that the UI response in Eclipse has become slower. You can see the problem by clicking around in the Team Artifacts view and opening different sub trees. Sometimes the response is fast, sometimes it takes several seconds to display the proper result. (To some extent, it was always like this with previous releases, but it became a lot worse.)

The source of problem is difficult to pinpoint, since there are so many different components involved (workstation, network, application server, database etc)

We fulfill all system requirements and the systems diagnostics report no problems. The performance health check widget report no issues either.

We have also timed the SCM Load operation which indicates that loading source code is faster in RTC 4.0.6 is actually faster than 4.0.1.

Could it simply be that RTC 4.0.6 is designed to behave differently and that is what users react to?

Anyway, it would be interesting to hear if anyone in the forum has similar experiences?

Kind Regards

Jocke thru Anders

Comments

Millard Ellingsworth commented Apr 18 '14, 5:30 p.m.

FORUM ADMINISTRATOR / JAZZ DEVELOPER

I didn't see this mentioned: What version of Eclipse? Did you update an existing client, get a new Eclipse client, or ?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Sumant Renukarya (1.1k●2●33●39) | answered Apr 16 '14, 6:13 a.m.

Hi Anders

I definitely do not believe the issue is due to the design or the updates in the RTC 4.0.6 Eclipse client that would be the factor for slow response.

I have upgraded to 4.0.6 but do not find similar behavior.

If this behavior was not see before upgrading and seen only after upgrading you might want to raise a PMR with IBM Support to look for the root cause.

Certain questions:

a. Is this specific to Eclipse client and not seen in web?

b. Specific to a project area or all?

c. What is the deployment topology? Where are the users located and the server?

d. Specific actions show slow response or all? If some actions, what are they?

e. What is the time in seconds when normal and time in seconds when slow?

f. What is the frequency of this? See for all users?

permanent link

Anders Persson (1●2●2) | answered Apr 17 '14, 3:21 a.m.

Hi Sumant

a. Eclipse only

b. All project areas

c. Single server with jts and ccm on WAS. Separate Oracle-server. User accounts in corporate Active Directory

d. Opening nodes in Team Artifacts can take 3-4 seconds the first time, then it seems to be cached. Opening plans is always slow in Eclipse, but fast in the web UI.

e. When it's fast, immediate response. When slow, 3-4 seconds, sometimes more.

f. All users have reacted to this after the upgrade.

/Anders

Comments

Sumant Renukarya commented Apr 18 '14, 12:32 p.m.

Anders

d. yes, web is the preferred and recommended method for opening plans than Eclipse.

Also, for opening nodes in Team Artifacts the time it takes depends also on the number of team areas that you have. How many you have for a project area, generally? Is it high?

If so, that might be one of the reasons but still doesn't warrant slowness, not seen before upgrade.

Maybe you should raise a PMR with IBM Support and see if they can drive to a logical conclusion?

It's all about the answers!

Related questions

Slow response in Eclipse after upgrading to RTC 4.0.6

2 answers

Your answer