Highlighted
Absent Member.
Absent Member.
1117 views

Siebel-specific performance test guidance

Please direct your replies to Rich Agnello (rich.agnello@hp.com) for the following request:

 

We concurrently performance test a suite of Siebel Customer Relationship Management applications (SFA, Advocate, Soleil, TAC, and Evolution).  At the individual app performance test level, we are currently experiencing persistent CPU, User Loss, Response Time, and app error trends.

 

The client has requested our assistance with Siebel-tailored performance test guidance for Ramp Up and other LoadRunner-specific parameters.  The objective is that we calibrate our performance tests specifically to the Siebel applications in question (as we might, e.g., for Web 2.0 or a specific RDBMS) so that these individual app trends do not impact our cumulative performance tests.

 

Any Siebel-specific performance test guidance you can provide?

0 Likes
3 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

I worked with Rick Kuehnel in another Siebel project for few months.

As we see a lot of activities on Server side during open Siebel and Logon, seems that they require more processing resources than usual.

So, we usually extend the cadence of the VUs entering into application to 1 VU each 5 or 10 seconds.

Remember that all WLP should follow requirements from application architects os other person with role to define how much load application would have in the Production environment. Ramp-up is not different, it simulates the number or users going to login in to application and in the real world, they would enter randonly but increasing the number of connections from 0 to average number, and can vary along the day.

If customer does not have defined rampup, we can just increase the interval of the users connecting until have CPU and memory usage ramping up accordingly.

If customer have defined rampup and we observe some issues like VUs failing to login, timeouts, etc, ... We should recomend application team to tune application servers, database, connection pools, network, disk and memory in order to reach target requirement.

In summary, it is expected to have ramp-up slow for Siebel application and we can look for best rampup by trying to balance between shortest rampup while transactions response time and server CPU are under normal level. Them, present to customer and see if they approve that as an acceptable time.

Best regards,

  'Eiju

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

I'd also add that you really need to follow the HP LR guidelines for Siebel performance testing (make sure that iteration 1 is in vuser_init() with the log in - if it's not subsequent iterations will fail

 

another possible issue is that the correlation/data is not correct (especially if you used auto-correlation and haven't been through the script line by line to check it)

 

why are the users failing? look at the extended logs (100K on error) and go back from there

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

For script debugging,

 A few places in the script , when auto correlated,  web_submit_data has issues with the data parameter, you might have to change it , below is what I did :

 

eg::1

"Name=SWEMethod", "Value=UpdatePrefMsg", ENDITEM,

 

//"Name=SWEMethod", "Value=Up{Siebel_Star_Array_Op31_rowid}PrefMsg", ENDITEM,

 

 

eg::2

 

"Name=SWEIPS", "Value=@0*0*5*0*0*3*0*8*interval4*150013*packUIStrings4*true9*alarmDate9*2/21/20125*SWEJI5*false3*now7*14:17:3", ENDITEM,
       

//"Name=SWEIPS","Value=@0*0*5*0*0*3*0*8*interval4*150013*packUIStrings4*true9*alarm{Siebel_Star_Array_Op31_rowid}9*2/21/20125*SWEJI5*false3*now7*14:17:3", ENDITEM,
       

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.