RTC 4.0.1 Eclipse client taking more time for save operation compared to RTC 3.0.1.3 client for the same work item
using RTC 4.0.1 and RTC 3.0.1.3 eclipse clients.
From office:
First used RTC 4.0.1 Eclipse client(Plain zip version). Added an extra space to Summary line and saved the Defect. Took 9 seconds.
Then used RTC 3.0.1.3 Eclipse client(Plain zip version). Added an extra space to Summary line and saved the same Defect. Took 3 seconds.
From home for the same operation:
RTC 4.0.1 client took 30 seconds and RTC 3.0.1.3 client took 3 seconds.
From web client it took less than 3 seconds from both office and home for the same save operation.
Seems slower the network, RTC 4.0.1 client save time increases rapidly where as RTC 3.0.1.3 holds quite steady.
Our customers have reported the same issue with RTC 4.0.1 eclipse client, after they were moved from RTC 3.0.1.3 version to RTC 4.0.1 version.
They also tried with Installation Manager version of RTC 4.0.1 Eclipse client which also exhibited same behavior.
Is this a known issue and Is there any settings in RTC 4.0.1 Eclipse client as a work around ?
One answer
Opening a support ticket might be a good idea.
In the meanwhile, you could start with comparing the metronome output for the "defect save" action using both 4.0.1 and 3.0.1.3 clients, to verify which component is taking more time.
See more about Metronome by clicking here.
I was just curious to see the behavior in my setup and it looks like the time taken in 3.0.1.3 is much lesser than in 4.0.1, but then, I am testing with the server and client on the same machine
Metronome behavior using:
1) 4.0.1 client connecting to 4.0.1 Server:
2) 3.0.1.3 client connecting to 4.0.1 Server
Comments
Thanks KrishnaKanth. Appreciate your quick response.
I also liked the way you had pasted the screen shot and the details. For some reason I could not paste or attach the image file for Metronome data I had, to the wiki.
In my case Edit operation, In RTC 4.0.1 client, (Server and Client are in separate machines)
IRepositoryRemoteService seems to be taking longer time 13.146 seconds(55%) followed by IAccessGroupService 8.961 seconds(37%). Rest were in decimal seconds and single digit percentage.
In RTC 3.0.1.3 had only one service, IWorkitemRepositoryService taking 1.999 seconds
It sounds like some kind of defect as it is reproduce-able irrespective of the environment. Is it not better to open a Defect ?
After deliberations within our team and some more tests, it seems there is real issue with RTC 4.0.1 client. We decided to open a Defect.
Defect 260354 is opened.
Hello Udaya
Glad that you like the way the results were presented.
I do agree with you on the differences sighted on the services invoked from the 2 clients, Submitting a support ticket would have helped us work with you on the setup that you have, but now that you have already submitted a defect lets wait for dev to get back to you.