{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"never","results":{"codes":[]},"settings":"","params":[]},"next":{"description":"","pages":[]},"title":"Realistic Load Simulation","type":"basic","slug":"realistic-load-simulation","excerpt":"","body":"During the tests Spatineo Performance typically sends thousands of test requests to the server(s) under test within a relatively short period of time. The requested area of the place-related requests, like the ones using WMS GetMap or WFS GetFeature operation, is varied from one request to another to ensure realistic test data. The variation algorithm leverages the same technology that’s used for Spatineo Monitor for generating test requests for continuous service availability monitoring. This request area variation also helps to verify the functionality and efficiency of any caching or tile pre-calculation scheme you might have configured to improve the service performance.\n\nWhen a new test is starting Spatineo Performance pre-generates all the test requests scheduled to be run during the test. It also ensures that there are enough fresh test servers available in our data centres to run the tests and collect their results for analysis. Each tests runs on a set of cloud-based high CPU and bandwidth servers dedicated for your particular test only to ensure exact and reliable measurements.\n\nTests in Spatineo Performance are designed simulate situations where a large number of users access the service at the same time rather than a few users using the service very intensively. This means that a number of new requests are started each second during the whole test regardless of whether the previously started requests have yet finished or not. Some other performance test solutions have chosen to create test load using a specific number of simulated users, each doing only one request at a time, and starting a new request as soon as the previous one is completed. Typical Spatial Web Service client applications often create more then one request at a time however to load the required data more efficiently in smaller pieces.\n\nOur decision of measuring the generated load only by the number of new requests created per second creates tests that are sometimes quite demanding for the servers because of the number of cumulating unfinished requests. We do this because it’s also what also happens in real life during the peak loads with a large number of simultaneous users. You can approximate the number of the simulated concurrent users for a test by dividing the amount of requests by the average request rate of your typical client applications when using the services.","updates":[],"order":13,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"5ccaf606c63d3c013b50f6ab","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Spatineo Performance","slug":"spatineo-performance","order":2,"from_sync":false,"reference":false,"_id":"5ccaf606c63d3c013b50f6a8","version":"5ccaf606c63d3c013b50f6bc","project":"544f6e49698ab40800b4f41e","createdAt":"2014-10-28T12:09:46.911Z","__v":0},"project":"544f6e49698ab40800b4f41e","user":"544f6e19cf9f86080080129a","version":{"version":"3.13","version_clean":"3.13.0","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["5ccaf606c63d3c013b50f6a6","5ccaf606c63d3c013b50f6a7","5ccaf606c63d3c013b50f6a8"],"_id":"5ccaf606c63d3c013b50f6bc","project":"544f6e49698ab40800b4f41e","__v":0,"forked_from":"5a5879a7086a05001c4317ac","createdAt":"2018-01-12T09:02:31.335Z","releaseDate":"2018-01-12T09:02:31.335Z"},"createdAt":"2014-10-28T20:14:36.038Z","githubsync":"","__v":0}

Realistic Load Simulation


During the tests Spatineo Performance typically sends thousands of test requests to the server(s) under test within a relatively short period of time. The requested area of the place-related requests, like the ones using WMS GetMap or WFS GetFeature operation, is varied from one request to another to ensure realistic test data. The variation algorithm leverages the same technology that’s used for Spatineo Monitor for generating test requests for continuous service availability monitoring. This request area variation also helps to verify the functionality and efficiency of any caching or tile pre-calculation scheme you might have configured to improve the service performance. When a new test is starting Spatineo Performance pre-generates all the test requests scheduled to be run during the test. It also ensures that there are enough fresh test servers available in our data centres to run the tests and collect their results for analysis. Each tests runs on a set of cloud-based high CPU and bandwidth servers dedicated for your particular test only to ensure exact and reliable measurements. Tests in Spatineo Performance are designed simulate situations where a large number of users access the service at the same time rather than a few users using the service very intensively. This means that a number of new requests are started each second during the whole test regardless of whether the previously started requests have yet finished or not. Some other performance test solutions have chosen to create test load using a specific number of simulated users, each doing only one request at a time, and starting a new request as soon as the previous one is completed. Typical Spatial Web Service client applications often create more then one request at a time however to load the required data more efficiently in smaller pieces. Our decision of measuring the generated load only by the number of new requests created per second creates tests that are sometimes quite demanding for the servers because of the number of cumulating unfinished requests. We do this because it’s also what also happens in real life during the peak loads with a large number of simultaneous users. You can approximate the number of the simulated concurrent users for a test by dividing the amount of requests by the average request rate of your typical client applications when using the services.