Difference between Loadrunner and performance center

Loadrunner	Performance Center
Loadrunner is a industry standard enterprise level load testing tool	Performance Center is a web enabled load testing tool
Resource management (VuGen scripts, scenarios and results) is local to the person, who is using the loadrunner tool on his local machine	Resource management is centralized, since it is web enabled
If there are multiple performance test engineers using the shared lab, there is lot of dilemma how to reserve the lab for a specific load test	Using performance center the lab machines can be reserved for a time slot
Using load runner optimum usage of virtual users licenses is a problem, if more than one load tester is involved	Virtual users can be reserved based on the time slot. So the user licenses can be optimally used in this case
A single load test at a time can be initiated from a loadrunner controller	Multiple load tests can be executed simultaneously using performance center
Versioning of the resources is not possible	Version of the resources is possible through performance center
Locally accessible platform	A Web-based, 24x7, globally accessible platform
Assets can be shared only on the local projects	Load test assets (VuGen scripts, results) can be shared across the project
Monitoring will help identify infrastructure issues	Infrastructure topology definition and monitoring to help identify infrastructure issues
There is no traceability in loadrunner	Performance requirements and defect traceability
There is no direct integration with HP Application Lifecycle Management and Business Availability Center	Integration with HP Application Lifecycle Management and Business Availability Center
Loadrunner is good, if you have a small load testing team sitting in one location	Performance center is good, if you have a large distrbuted load testing team sitting in different locations

Performance Center Interview Questions and Answers | LRE Interview Questions and Answers

1. Tell something about Performance Center?

Answer: Performance Center is an enterprise-level performance testing tool developed by Micro Focus. It provides a centralized platform for planning, executing, and analyzing performance tests for applications, websites, and systems. Performance Center offers features for test management, resource allocation, monitoring, and reporting, making it a comprehensive solution for performance testing needs.

2. Which of the cases Performance Center will be chosen over LoadRunner?

Answer:  Performance Center is typically chosen over LoadRunner in scenarios where organizations require centralized test management, collaboration among distributed teams, scalability for large-scale testing, and integration with other ALM (Application Lifecycle Management) tools.

3. What are the types of access sites available in Performance Center?

Answer:  The types of access sites available in Performance Center include:

   - Lab Management Site

   - Performance Center Site

   - Business Process Monitor (BPM) Site

4. What is a User Site in Performance Center?

    Answer:  A User Site in Performance Center refers to the web interface where users can access and interact with Performance Center functionalities, such as creating and scheduling tests, monitoring test executions, and analyzing test results.

5. What is a Host in Performance Center?

 Answer:  In Performance Center, a Host refers to a physical or virtual machine that hosts Load Generators or other Performance Center components. Hosts are responsible for executing performance tests, generating virtual user load, and collecting performance metrics.

6. Can one system act as a Controller and Load Generator in Performance Center?

 Answer:  Yes, in Performance Center, a single system can be configured to act as both a Controller (responsible for test management and execution) and a Load Generator (responsible for generating virtual user load).

7. What is a Timeslot in Performance Center?

     Answer: A Timeslot in Performance Center represents a predefined period during which a performance test is scheduled to run. It defines the start and end times for test execution and resource allocation.

8. What is the significance of using Timeslots in Performance Center?

   Answer:   Timeslots in Performance Center help allocate resources efficiently by allowing users to schedule performance tests during specific time windows. They ensure that test executions do not overlap and that resources are available as per the defined schedule.

9. How to create Vuser Scripts in Performance Center?

    Answer:  Vuser scripts in Performance Center are created using Micro Focus Virtual User Generator (VuGen) tool. Users can record user actions, parameterize data, and enhance scripts with custom logic using VuGen's scripting interface.

10. What are the steps followed to upload VuGen scripts in Performance Center?

    Answer:   To upload VuGen scripts in Performance Center, follow these steps:

    - Log in to Performance Center.

    - Navigate to the "Test Plan" module.

    - Click on "Scripts" and select "Upload Script."

    - Browse and select the VuGen script files (.usr) to upload.

    - Specify script details such as script name, type, and description.

    - Click "Upload" to upload the scripts to the desired project.

Certainly, here are the answers to the next set of questions:

11. How to create test scripts directly in Performance Center?

    Answer:   Test scripts can be created directly in Performance Center using the "Script Editor" feature. Users can define script actions, parameters, and logic within the Performance Center web interface without needing to use external tools like VuGen.

12. What is a monitor profile in Performance Center?

     Answer:  A monitor profile in Performance Center defines the configuration settings for monitoring system resources and application performance during test execution. It includes parameters such as monitoring intervals, metrics to be collected, and thresholds for alerts.

13. How to add monitor graphs from Performance Center?

    Answer:   Monitor graphs can be added to Performance Center by configuring monitor profiles and associating them with performance tests. Users can select the desired monitor metrics and graph types to be displayed during test execution and analysis.

14. What is auto start viewer in Performance Center?

    Auto Start Viewer in Performance Center is a feature that automatically launches the Analysis tool (Analyzer) upon completion of test execution. It enables users to quickly analyze test results and generate performance reports without manual intervention.

15. How to configure auto start viewer in Performance Center?

     Answer:  Auto Start Viewer can be configured in Performance Center by enabling the option in the user preferences or project settings. Users can specify the conditions under which Analysis should be automatically launched, such as after test completion or at specific times.

16. What is the significance of options in Performance Center?

      Answer: Options in Performance Center allow users to customize various settings and configurations according to their requirements. These options cover a wide range of functionalities such as test execution, monitoring, reporting, and user preferences.

17. Where the settings for Transaction Data and Server Resource Monitors will be set in Performance Center?

    Answer:   The settings for Transaction Data and Server Resource Monitors can be configured within the Monitor Profile in Performance Center. Users can define the specific transactions to monitor and select the server resources (e.g., CPU, memory, disk) to collect data from.

18. What are the runtime settings that can be set in Performance Center options?

     Answer:  Runtime settings in Performance Center options include configurations related to test execution, such as the maximum number of concurrent users, duration of test runs, ramp-up and ramp-down periods, and logging levels.

19. How to set the timeout settings for load generator and Vuser in Performance Center?

     Answer:  Timeout settings for load generator and Vuser in Performance Center can be adjusted in the LoadRunner runtime settings. Users can specify the timeout values for various operations, such as connection timeouts, response timeouts, and script execution timeouts.

20. What is the debug information setting that can be set in Performance Center options?

     Answer:  The debug information setting in Performance Center options allows users to specify the level of detail for debug messages generated during test execution. Users can choose from different verbosity levels, such as minimal, standard, or verbose, depending on their debugging needs.

21. How multiple IP address allocation per process or thread can be set in Performance Center?

     Answer:  Multiple IP address allocation per process or thread can be configured in Performance Center by adjusting the IP allocation settings in the LoadRunner runtime settings. Users can specify the number of IP addresses to allocate per process or thread to simulate different virtual users with distinct IP addresses.

22. How to switch from one project to the other without logging out from Performance Center?

    Answer:   In Performance Center, users can switch from one project to another without logging out by selecting the desired project from the project dropdown menu available in the top navigation bar. This allows users to seamlessly navigate between different projects within the same Performance Center session.

23. How to create a new load test in Performance Center?

     Answer:  To create a new load test in Performance Center, follow these steps:

    - Log in to Performance Center.

    - Navigate to the "Test Plan" module.

    - Click on "New Test" and select "Load Test."

    - Provide details such as test name, description, and associated project.

    - Configure test settings including load generator allocation, scheduling, and monitoring options.

    - Click "Save" to create the new load test.

24. How to enable spoofer in Performance Center?

    Answer:   Spoofer can be enabled in Performance Center by configuring the script runtime settings in VuGen. Users can specify the spoofer settings, including the type of spoofing (e.g., DNS, IP), the spoofed values, and the behavior during script execution.

25. How to pause a scheduler at load test start in Performance Center?

   Answer:    To pause a scheduler at load test start in Performance Center, users can configure the scheduling options in the test settings. By setting the start time of the test to a future date and time, the scheduler will automatically pause until the specified start time is reached.

26. What are the options available in assigning the load generators to groups in Performance Center?

    Answer:   The options available in assigning load generators to groups in Performance Center include:

    - Manual assignment: Users can manually assign load generators to specific groups based on their requirements.

    - Automatic assignment: Performance Center can automatically allocate load generators to groups based on predefined criteria such as geographic location, hardware specifications, or workload distribution.

27. How to set and change the group size by number in Performance Center?

      Answer: Group size by number can be set and changed in Performance Center by adjusting the group settings in the test configuration. Users can specify the desired number of load generators to be included in each group and modify the group size as needed.

28. What is the advantage of using group size by percentage option in Performance Center?

     Answer:  The advantage of using group size by percentage option in Performance Center is that it allows for dynamic allocation of load generators based on the total number of available load generators. This ensures that the workload is evenly distributed across groups, regardless of the total number of load generators in use.

29. How to add multiple groups in Performance Center load test?

      Answer: Multiple groups can be added in Performance Center load test by configuring the group settings in the test configuration. Users can specify the number of groups to be created and define the allocation criteria for each group, such as geographic location or hardware specifications.

30. What is the significance of using start time options in Performance Center scheduler?

 Answer:  The start time options in Performance Center scheduler allow users to schedule test executions at specific dates and times. This enables users to plan and coordinate test runs according to their preferred schedule, ensuring that tests are executed during off-peak hours or at times of low user activity.

31. What is the importance of utilizing schedule options in the Performance Center scheduler?  

Answer:   Schedule options in the Performance Center scheduler are crucial for defining when tests will run, enabling users to schedule tests during off-peak hours, allocate resources efficiently, and ensure that tests do not interfere with regular system usage. This allows for better resource utilization and more accurate performance testing results.

32. What is the significance of leveraging run mode options in the Performance Center scheduler?

 Answer: Run mode options in the Performance Center scheduler dictate how load tests are executed, including options like standalone mode for isolated test runs, manual mode for user-controlled execution, and automatic mode for scheduled executions. These options offer flexibility in test execution, enabling users to tailor testing strategies to their specific requirements and constraints.

33. What actions are available in the Performance Center global schedule?

 Answer: The Performance Center global schedule offers various actions, including scheduling new tests, modifying existing test schedules, canceling scheduled tests, and viewing the status of scheduled tests. These actions provide users with comprehensive control over test scheduling and execution within the Performance Center environment.

34. What is the significance of each action in the Performance Center global schedule?

 Answer: Each action in the Performance Center global schedule serves a specific purpose:

     - Scheduling new tests allows users to define when and how tests will be executed.

     - Modifying existing test schedules enables adjustments to test parameters and execution timing.

     - Canceling scheduled tests provides a means to halt tests that are no longer necessary or relevant.

     - Viewing the status of scheduled tests offers insights into test execution progress and results, facilitating informed decision-making.

35. How can monitors be added in a Performance Center load test?

  Answer: Monitors can be added to a Performance Center load test by configuring monitor profiles within the test settings. Users can specify the types of monitors to be included, such as server performance, database activity, or network metrics, and customize monitoring parameters according to test requirements.

36. What information does the search results module display in Performance Center?

Answer: The search results module in Performance Center displays relevant search matches based on user-defined criteria. It provides a consolidated view of search results across various Performance Center modules, facilitating efficient data retrieval and analysis.

37. How can personal information be updated in Performance Center?

Answer: Personal information in Performance Center can be updated by accessing the user profile settings. Users can modify details such as contact information, preferences, and notification settings to ensure accurate and up-to-date account information.

38. Where can recently run load tests be viewed in Performance Center?

Answer: Recently run load tests can be viewed in the "Recent Runs" section or tab within the Performance Center interface. This section typically provides a chronological list of recently executed load tests, allowing users to access test results and performance data easily.

39. Where can currently running load tests be monitored in Performance Center?

Answer: Currently running load tests can be monitored in real-time through the "Active Sessions" or "Current Executions" section of the Performance Center dashboard. This section displays active test sessions, including details such as test name, status, duration, and resource utilization.

40. Where can upcoming reserved timeslots be viewed in Performance Center?

 Answer: Upcoming reserved timeslots can be viewed in the "Scheduled Runs" or "Reserved Timeslots" section of the Performance Center scheduler. This section provides a calendar or list view of reserved timeslots, indicating when tests are scheduled to run and which resources are allocated for each session.

   

41.  What is the dashboard section of Performance Center and where can it be accessed?

Answer: The dashboard section of Performance Center provides a centralized view of key performance metrics, test statuses, and project insights. It can be accessed by navigating to the dashboard tab or section within the Performance Center interface.

42.  How can service level agreements be set in Performance Center?

 Answer: Service level agreements (SLAs) in Performance Center can be set by defining specific performance thresholds and targets for various test metrics. Users can configure SLAs within test settings or project configurations to ensure that performance goals are met during testing.

43.  What types of service level agreements are available in Performance Center?

Answer: Performance Center offers various types of service level agreements, including response time targets, throughput requirements, error rate thresholds, and resource utilization limits. These SLAs can be customized to align with the performance objectives of each test scenario.

44.  How can load test results be downloaded from Performance Center?

 Answer: Load test results can be downloaded from Performance Center by accessing the test run or execution summary and selecting the option to export results. Users can choose the desired format (e.g., PDF, CSV) and specify the data range for the download.

45.  How can results be analyzed in Performance Center?

Answer: Results in Performance Center can be analyzed using built-in analysis tools or by exporting data to external analysis software such as LoadRunner Analysis. Users can examine performance graphs, transaction response times, error details, and other metrics to gain insights into test performance.

46.  What reports are generated by Performance Center?

 Answer: Performance Center generates various reports, including test execution summaries, trend analyses, performance comparison reports, and detailed transaction reports. These reports provide comprehensive insights into test results, trends, and performance metrics.

47.  How can test scripts be uploaded directly from VuGen to Performance Center?

 Answer:  Test scripts can be uploaded directly from VuGen to Performance Center by using the "Upload Script to Performance Center" feature within VuGen. Users can specify the target project and folder in Performance Center for the script upload.

48.  How to import scripts from one project to another in Performance Center?

   Answer: Scripts can be imported from one project to another in Performance Center by using the import/export functionality within the Performance Center interface. Users can select the desired scripts and specify the destination project for the import process.

49.  How can uploaded scripts be edited in Performance Center?

Answer: Uploaded scripts in Performance Center can be edited by accessing the script details or properties within the project. Users can modify script parameters, settings, and configurations as needed using the built-in script editor.

50.  How to import monitors from one project to another in Performance Center?

 Answer:  Monitors can be imported from one project to another in Performance Center by using the import/export functionality similar to script import. Users can select the monitor profiles to be imported and specify the destination project for the import process.

51.  What are the prerequisites for importing scripts and monitor profiles in Performance Center?

Answer:  Prerequisites for importing scripts and monitor profiles in Performance Center include appropriate user permissions, access to both the source and destination projects, and compatibility between the Performance Center versions used.

52.  How can more monitors be added to an existing monitor profile in Performance Center?

Answer:  Additional monitors can be added to an existing monitor profile in Performance Center by editing the profile settings within the project. Users can specify the new monitors to be included and configure their parameters accordingly.

53.  How to add a project to be part of auto start viewer in Performance Center?

 Answer: To add a project to be part of the auto-start viewer in Performance Center, users can configure project settings to enable automatic startup when Performance Center is launched. This ensures quick access to frequently used projects.

54.  What is the difference between a project and a load test in Performance Center?

Answer:  In Performance Center, a project is a container for organizing test assets, including scripts, monitor profiles, and test configurations. A load test, on the other hand, is a specific test scenario within a project that defines the workload and parameters for performance testing.

55.  How to assign virtual load generators to groups in Performance Center?

Answer: Virtual load generators can be assigned to groups in Performance Center by configuring host allocations within the project settings. Users can specify which groups of load generators will execute tests and allocate resources accordingly.

56. How to analyze load test results from Analyzer in Performance Center?

 Answer: Load test results can be analyzed from Analyzer in Performance Center by exporting the test results data from Performance Center and opening it in LoadRunner Analysis. Users can then use Analysis tools to perform in-depth performance analysis and generate custom reports.

57.  How to publish load test results to the dashboard in Performance Center?

Answer:  Load test results can be published to the dashboard in Performance Center by selecting the option to publish results after test execution. Users can choose the relevant dashboard and specify the metrics and graphs to be displayed.

58.  What is the prerequisite for publishing load test results to the dashboard in Performance Center?

Answer: The prerequisite for publishing load test results to the dashboard in Performance Center is having appropriate permissions to access and modify dashboard settings. Users must also ensure that the necessary test results are available and ready for publishing.

59.  What details are displayed after a load test is published to the dashboard in Performance Center?

 Answer: After a load test is published to the dashboard in Performance Center, details such as test name, execution status, performance metrics (e.g., response time, throughput), and any associated graphs or charts are displayed. This provides stakeholders with a quick overview of test results and performance trends.

60. How would you approach diagnosing and troubleshooting a performance bottleneck in a distributed application environment using Performance Center?"

Answer:  effectively diagnose and troubleshoot a performance bottleneck in a distributed application environment using Performance Center, I would follow a systematic approach:

• Identify Performance Metrics: Begin by gathering comprehensive performance metrics from all components of the distributed application. This includes server-side metrics such as CPU utilization, memory usage, disk I/O, and network throughput, as well as client-side metrics like response times, transaction rates, and error rates.
• Analyze Load Test Results: Utilize Performance Center to conduct load tests that simulate real-world user interactions with the application. Analyze the load test results to identify any performance degradation or bottlenecks under load conditions. Pay close attention to response times, throughput, and resource utilization metrics.
• Correlate Performance Data: Correlate the performance data collected from different components of the distributed application to identify any patterns or correlations. Look for discrepancies or anomalies in performance metrics that may indicate potential bottlenecks.
• Isolate Bottleneck: Once potential bottlenecks are identified, isolate the root cause of the performance bottleneck by systematically narrowing down the scope of investigation. This may involve analyzing specific transactions, functions, or components of the application to pinpoint the source of the performance issue.
• Use Diagnostic Tools: Leverage Performance Center's diagnostic tools and performance monitoring features to further investigate the identified bottleneck. Use tools such as transaction tracing, database monitoring, and network analysis to gain deeper insights into the performance of individual components.
• Implement Performance Tuning: Based on the findings from the diagnostic analysis, implement performance tuning strategies to optimize the performance of the distributed application. This may involve adjusting configuration settings, optimizing code, or scaling resources to alleviate the bottleneck.
• Validate Improvements: Re-run load tests in Performance Center to validate the effectiveness of the performance tuning efforts. Monitor performance metrics closely to ensure that the identified bottleneck has been resolved and that overall application performance has improved.
• Document Findings: Document the diagnostic process, findings, and performance tuning recommendations for future reference. This documentation will serve as a valuable resource for troubleshooting similar issues in the future and for sharing insights with other team members

Difference between Thick Client and Thin Client

Thick Client Vs Thin Client:

Thin Client	Thick Client
Mostly it is a web based client. Will be accessed through a common client called browser	It will be accessible through client software which is installed locally
Business logic will be there in middleware’s or application servers.	Business logic will be installed in the local machine.
When the URL is accessed most of the business logic will be executed on the server. And some client side processing and rendering happens within the browser.	When the client get installed all the business logic of the application installed locally
Thin client uses stateless connections. For each request connection will be opened and after the response it will be closed	Thick client uses dedicated connections
Thin clients are slower in response • Connection needs to be opened explicitly for each request • Pages needs to be downloaded from presentation layer • Data needs to be retrieved from the DB • Business logic related processing will be happening in the middle wares or application servers	Thick clients are faster in response • most of the processing happens locally • Connections will be closed only explicit logouts
Thin clients will be used by the external users. Ex: Bank customers	Thick clients will be used by the internal users most of the times: Ex: Bank employees and customer support executives