Pinned topicWhere should RDz improve performance?

‏2010-08-21T01:41:40Z
|Tags:

Answered question
This question has been answered.

Unanswered question
This question has not been answered yet.

The RDz lab team is trying to prioritize where we will do some performance work. We have our own opinions, but thought it would be good to get some input from real users. Here are my pseudo-prioritized thoughts. Comment if you agree, have a different priority, or have things that are not listed:

Performance work priorities

Editor Open time (RSE double-click...wait...ready for edit)

Content assist speed

Large member/file open time

Hover-help popups

Workbench startup time

z/OS details view sorting

Remote search/text search

RSE connect time

local syntax check

I did not list "Filter creation and display" as I hope the Large PDS support added in 7.6.1 provided relief for you all. If we still need to work on that please list it.

Re: Where should RDz improve performance?

‏2013-06-17T03:58:50Z

This is the accepted answer.
This is the accepted answer.

from my experirnce, #1 Large member/file open time and #7 Remote search/text find are the important. Especially, the remote search function is not only slow, but sometime abended without returning the result in case the target members are over 10,000.