While posting reversal JV in General Journal, the application goes into a non-responding state. It takes around 2 hrs and 40 mins to post around 2000 lines. It is simple multiple-line JV with Reversal ticked and reversal Date specified.Since this is a Reversal JV, system creates additional 2000 lines and then post the JV.
It is AX 2009 SP1 application with very low level of customization, with following additional details.
CPU: Intel(R) Xeon(TM) CPU 2.4GHz*2
HDD: 146.8GB X 2, 300GB X 2
RAM: 4GB
Database size 4 GB
To solve the performance issue we undertook following set of activity:
1. We worked towards Rebuilding indexes as well as analyizing SQL plans and missing indexes. The cost of selecting an index from plan were good.
2. We tried using the code-profiler to check on the method calls that might be taking time. During analysis we found that in certain areas we might improve the codes, but this is having very little impact on the overall posting time.
3. We even tried testing the application after doing a mock upgrade to the latest version, but the timings remain the same.
4. We collected certain Perfmon counter details to check if current status of the server. The reponse of the server was good.
5. To rule out any issue of caching we tested the application on high end server but timings remained the same.
Hence based on the observation we have not made much of improvement. Few of the queries that I have
1. What is the typical posting time that one have during posting of a JV, so that we can benchmark and test against our findings (?).
2. How do one proceed with performance trouble shooting (?)
It is a request if you can share your experience here.