1 / 12

Alliance Alliance Performance Status – CDR module

Alliance Alliance Performance Status – CDR module. Régis ELLING / Sébastien ROECKEL February 2011. Alliance – Performance Status - Objectives. Describe the performance enhancements with objectives: Current results of the Stress tests with highlights on slow features.

lloyd
Download Presentation

Alliance Alliance Performance Status – CDR module

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AllianceAlliance Performance Status – CDR module Régis ELLING / Sébastien ROECKEL February 2011

  2. Alliance – Performance Status - Objectives Describe the performance enhancements with objectives: • Current results of the Stress tests with highlights on slow features. • Remaining or on-going actions needed to enhance performances.

  3. Stress Tests – CDRStrategy & results

  4. Alliance – Performance Status – Stress Tests - Strategy Strategy: • Stress tests have been updated and completed to have a global overview of the Alliance OEFE application, testing AFE Order, B2B and now also CDR & CREQ. • Considering the high number of scenarios and also to ease the analysis, we have: • Executed the runs on a feature by feature basis (per module): all the scenarios related to a given functionality of the application are executed. This way it is also possible to optimize a “module” (errors, response times, load …). • To execute all the scenarios at the same time: only once all the modules of the Alliance application have been validated. • The following slides present the results for the CDR module only. • The last stress test and following results are from the R3.5.

  5. Alliance – Performance Status – Stress Tests results - CDR (1/4) CDR Management • The following features are included in this part of the test: • CDR: Create & attach documents, submit to OM, search with high number of results, low number of results, register the CDR by Sales Order creation. • Strategyapplied: • 2 hours of execution of scenarios whileincreasing the number of users up to 50 during 1st hour, then up to 84 for the 2ndhour. • Crash test performed to see the behaviour of the modules under high activity.

  6. Alliance – Performance Status – Stress Tests results - CDR (2/4) Errors during the stress test • The error rate is very low, apart from the CSUB06_Submit. • The errors related to the CSUB06_Submit are because of the way the scenarios are executed by the Stress test tool. For a “normal” user errors of this type cannot happen.

  7. Alliance – Performance Status – Stress Tests results - CDR (3/4) Global Response times during the stress test Top 10 highest response times • The response times are stable and correct, the transaction CSUB08_Save is the slowest one but remains stable. • This run has a very small impact on the server’s activity (less than 30 %). SQL server is the most loaded (between 20-30%).

  8. Alliance – Performance Status – Stress Tests results - CDR (4/4) Global Response times during the crash test (600 users) CPU load during crash test • Up to 200 users the response times are stable. At approx 300 users the transactions CSM03_SearchSubmit, CSS03_SearchSubmit, CSUB03_Search and CSUB08_Save have increasing response times. The response times for these transactions continue to grow regularly up to 600 users. The other response times are relatively stable. • The CPU load on the web servers increases regularly up to 300 users and is stable (around 35 %). • The CPU load on the SQL server is increasing faster up to 100 % (for approximately 400 users). • The limit of the CDR module is located between 300 and 400 users.

  9. Alliance – Performance Status – Stress Tests results - CDR - Conclusions Conclusions • There are no major problems with the CDR module: • Low error rate • Response times are low • The impact on the server resources is limited • The limit of the CDR module is between 300 and 400 users There is no problem identified on this module needing performances enhancements.

  10. Remaining or on-going actions

  11. Alliance – Performance Status – Optimizations (1/1) Attach documents to CDR • Whenuploading a document to a CDR, the country in which the action isperformedwith files of similar size show a greatdifference in the response times. • This isrelated to the factthat the files superior to a defined size and cut in smallerpieces for transfer and increase the latencyeffect. • Analysis to beperformed to see if transfer of files canbeoptimizedespecially for long distance countries.

  12. www.alcatel-lucent.com www.alcatel-lucent.com

More Related