on 06-09-2016 2:54 PM
Hello Andrey,
In order to understand which nested call(s) contributed to high processing time (3 seconds that you highlighted), I would suggest to make use of a JVM Profiler tool (for example, SAP JVM Profiler that is a part of SAP JVM Supportability Tools, or any other compatible Java Profiler tool like YourKit, JProfiler, etc.) and execute performance hotspot analysis for the Java mapping in question. Having done so, you will get detailed breakdown of method calls invoked by the profiled mapping and identify which nested calls have the longest execution time and also highest occurrence. Based on this information, it can be analysed further if mapping performance can be improved.
For SAP JVM Profiler, there are good materials on SCN that provide illustrations and demos for this kind of profiling - for example, .
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Andrey,
Why the Java code is used.Please post the code to assist further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.