We are in the process of upgrading from 6.2 to 7.2 at our customer. We have an outstanding issue in 6.2 that if the end user keeps using the same session for his retention flows over a period of time, the performance slows due to the fact that the IS Fact response list is growing and the page copy to move it at the end of our request is slowing down - less than a second on the page copy on the first request but over 2 minutes if the user uses the same session for 15 requests - not usually done - usually the agents start a new session per user, so not a major issue.
That said, in our 7.2 upgrade environment, we do not notice the slow down. Does that mean something was done to improve page copy performance in 7.2. I don't want to give that as an explanation to my client without some confirmation of that. If anyone knows if performance in page-copy was improved between 6 and 7, please let me know.
Thanks Santanu for the quick response. I did just read the information given at the sites pointed to by the links above. I do see performance has greatly improved across the board. I am not sure that I see where a Page-Copy has been improved.
Looking at the underlying generated code in both 6.2 and 7.2, I still do not understand why 7.2 is faster - on the Page-Copy itself - I am sure 7.2 has much improved performance overall. But the 12 or 13 lines of code to do the page copy is the same in 6.2 and 7.2. Maybe the ClipboardPage.putAll method is improved. I will check my data in 7.2 to see if there is less - should not be the case, but we may have other issues involved here. If the size of the data is the same, I will tell the customer that overall performance improvements in 7.2 make the issue go away - without being too specific, and assume the ClipboardPage.putAll performance was improved.
I did notice - at the suggestion of one of our other consultants - that I could use Property-Set instead of Page-Copy in the code that is slowing down. I tried it and it was much faster - orders of magnitude. And I had all the data as far as I could tell - though it was well nested. But I am not sure I can do that in every case.