![Contents of Presentation ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Neoload overview
Similar a Neoload overview (20)
Neoload overview
- 1. NeoLoad Tool for Performance Testing
Notas del editor
- Link for NeoLoad overview: http://www.neotys.com/product/demo-neoload.html#advanced
- NeoLoad records and replays browser requests to the server, which means that NeoLoad: Can simulate requests made by components such as plug-ins, Java applets, ActiveX, Flash, animations,... Cannot simulate local actions such as updating a graphical component using client-side JavaScript.
- Business Transaction: A virtual user container groups the different web pages that make up a "business transaction". In other words, a container is a set of web pages that carry out a business exchange. A typical example of this type of container is the set of pages used to connect to the application. These containers are clearly marked in the test results to make analyzing download times easier.
- A population is a group of virtual user types which allows the application to be tested using different business actions. One typical example is when testing a ebusiness website with 90% of users browsing the catalog and 10% making an online purchase.
- Load variation policy: Defines what type of load you need to put on. Duration policy: How do you want to stop the test, manually, after n iteration or after some specified amount of time. Basically we set load profile here.
- Runtime information changes/gets modified with time. The parameters which are mentioned here have been previously defined during DESIGN>>Monitor >> Assign a new machine to be monitored >> Select various counters. Monitors the load generators' activity: • Host - Machine running the load generator. • Virtual Users - Number of virtual users currently being run by that load generator. • Hit Rate - Average hit rate generated by that load generator. • Errors - Current error rate (number of errors per second). • CPU Load - CPU load for the machine hosting the load generator. • Memory Used - Memory used, expressed as a percentage of the memory allocated to the load generator program (the program's default memory allocation is 384Mb). • Throughput - Throughput in Megabits per second for the network interface used on the load generator. If the CPU Load or Memory Used figure regularly exceeds 90%, this indicates that the load generator is overloaded. Run the test with fewer virtual users or a longer think time, or use additional load generators.