It’s critical to note that script design can have an adverse impact on LG load capacity. Having gigabit network cards (NIC) for bandwidth will alleviate LG communication and traffic bottlenecks. Having 12-16 GB of physical RAM, and allocating one-fourth to one-half heap space for the JVM is recommended. Having a quad-core processor (or better), rather than dual-core, is a must for heavy load testing today. Kerberos authentication (massive memory overhead), and XPATH extractions.Storage location, complexity of design, protocols used. CPU capability and bandwidth (local hardware, and network between).Allocated heap space to the Java virtual machine (JVM).When figuring out LG capacity and performance, you should keep some core factors in mind: Ultimately, addressing what each of your LGs is capable of handling is the key. For example, if the internal machines you’re using for LGs have 1,000 virtual user capacity based on current scripts and configuration, and you need to run a 10,000 VU load test, you will need 10 LG machines. Once the capacity for a single load generator is known, you can then extrapolate the number of total load generators (LG) needed to meet load test demand. The following is a guide to help you understand and discover scaling your resources to meet load testing demand using Tricentis NeoLoad. No manager or company wants to suffer the consequences of wasted time and budget as a result of failed testing due to unused or missing resources. As you prepare your scripts, you’re probably also thinking about load generator requirements - differentiation between them, their capacity, and how many needed. Your virtual user (VU) load is significantly higher than anything you’ve tested before. You’ve got complex load tests coming up with a deadline.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |