The Stress Test Tool. TCPOS The Stress Test tool Page 1/14

Transcription

1 The Stress Test Tool TCPOS The Stress Test tool Page 1/14

2 This document and all of its contents are protected by copyright. All rights are expressly reserved including those of duplication, reproduction, translation, microfilming, storage on electronic media and processing in electronic form. TCPOS is a registered trademark of TCPOS SA. Microsoft, Windows, Windows XP, Windows Embedded POSready, Windows Vista, Windows 7, Windows 8, Windows Embedded POSready 7, Windows 2003 Server, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 RC2, Microsoft SQLServer 2005, Microsoft SQLServer 2008, Microsoft SQLServer 2008 R2, Microsoft SQLServer 2012, Microsoft SQLServer 2012 Express Edition 32 bit & Microsoft SQLServer 2012 Express Edition 64 bit, Microsoft SQLServer 2014, Microsoft SQLServer 2014 Express Edition 32 bit & Microsoft SQLServer 2014 Express Edition 64 bit, Windows Mobile 2003, Windows Mobile 5.0, Windows CE.NET 4.0, Windows CE.NET 4.2, Windows CE 5.0, Windows CE 5.1, Windows CE 5.2, Windows Embedded CE 6.0, Windows Embedded CE 6.1, Windows Embedded CE 6.5, Windows Embedded CE 6.0 R2 and Windows Embedded CE 6.0 R3 are registered trademarks of Microsoft Corporation. Oracle 10gTM, Oracle 11gTM, Oracle 11g R2TM, Oracle 11 XE Express edition 32 bittm, Oracle 12cTM, are trademarks or registered trademarks of Oracle Corporation. The PostgreSQL 9.1, The PostgreSQL 9.3 are a registered trademark of The PostgreSQL Global Development Group. Android is a registered trademark of Google Inc. All other company, product and brand names are trademarks or registered trademarks of their respective owners. The information featured in this document may be subject to change without notice at any time. Copyright TCPOS SA, All Rights Reserved. Document info Document ID: Tool_StressTest_1.0 Document date: June 2016 Document version: 1.0 Distribution: This electronic file is the original and supersedes any printed copy Switzerland TCPOS SA - Lugano Centro Galleria 2, Via Cantonale 2c CH-6928 Manno Tel. +41 (0) Fax +41 (0) Germany TCPOS GmbH Völklingen (Saarbrücken) Saarwiesenstr. 5 D Völklingen Tel. +49 (0) Fax +49 (0) France TCPOS France - Paris 9 b Rue de la Sablière F Gennevilliers Tel. +33 (0) Italy ZUCCHETTI TCPOS Srl - Milan Via A. De Gasperi Rho (MI) Tel Fax: TCPOS SA - Lausanne Route Z.I. La Vulpillière 61B CH-1070 Puidoux Tel. +41 (0) Fax +41 (0) TCPOS SA - Zürich Giessenstrasse 15 CH-8953 Dietikon Tel. +41 (0) Fax +41 (0) USA TCPOS U.S.A. Inc. - Reno 1875 Plumas Street Ste 5 Reno, NV Tel +1 (775) North America TCPOS North America Toronto 2225 Sheppard Ave. East (Atria III Building) Suite 901 Toronto, ON Canada M2J 5C2. Tel. +1 (416) Fax +1 (416) Latin America TCPOS SA Buenos Aires Portela 407, 2ºC C1406FDI Buenos Aires- Argentina Tel (11) Fax +1 (416) China TCPOS ASIA Shanghai No.400 Fangchun Road China (Shanghai) Pilot Free Trade Zone Tel TCPOS The Stress Test tool Page 2/14

3 Index Index... 3 Foreword... 4 This tool guide... 5 Aim of the tool... 5 Part 1: Implementation... 6 Tool modules... 7 Part 2: Workability... 8 Connection string... 9 Transaction test tab...9 Database snapshot test tab...11 Get card data tab...12 Connections tab...13 Shifts tab...14 TCPOS The Stress Test tool Page 3/14

4 Foreword This tool guide Aim of the tool TCPOS The Stress Test tool Page 4/14

5 This tool guide This document describes the features of the Stress Test tool. Aim of the tool The Stress test tool is aimed for testing TPCOS software activity within or beyond the limits of normal operation. It tests the performance of the TCPOS ServerService in particular situations. This application is composed of five tabs, each of them dedicated to the test of a particular feature: Tab Transaction test tests the requests executed by FrontEnd to the ServerService when transmitting data related to transactions to the database; Tab Database snapshot test tests the requests executed by FrontEnd to the ServerService when downloading the local database used by tills; Tab Get card data tests the requests executed by FrontEnd to the ServerService when trying to retrieve data about customer cards read on tills; Tab Connections tests the maximum amount of connections handled (software and hardware limits); it also checks the possible pending requests or discarded connections; Tab Shifts tests the requests executed by FrontEnd to the ServerService when transmitting data related to shifts to the database. In each tab there is the possibility to set the parameters in order to test the actual configuration of the environment, or to push the system beyond the limits in order to understand its break point. TCPOS The Stress Test tool Page 5/14

6 Part 1: Implementation Tool modules TCPOS The Stress Test tool Page 6/14

7 Tool modules The modules composing this tool are described in the related wiki.tcpos.com article Please refer to it for further information. TCPOSwiki article: Technical:Stress Test Tool TCPOS The Stress Test tool Page 7/14

8 Part 2: Workability The Stress test tool TCPOS The Stress Test tool Page 8/14

9 Connection string Specify the DB connection string to the ServerService (the same as the one stored in the *.ini file) in the format For example possible connection strings are: Transaction test tab This tab is used to test the requests executed by FrontEnd to the ServerService when transmitting data related to transactions to the database. The result highlights how many transactions can be successfully processed in a predefined time and how many concurrent clients may be handled by the reviewed environment. After filling the parameters, press the Start button to start the test. Field Transaction file Description Select the file, generated by FrontEnd, containing the data of the transaction to be used as sample. The structure of this file corresponds to the one of the files usually generated by FrontEnd and stored in the local directory Frontend\DbTransactions\yyyy-mm-dd\DbTrn dd-yy-mm #transactionnumber.xml. TCPOS The Stress Test tool Page 9/14

10 Parallel threads Delay between consecutive requests (ms) Execution seconds Transactions year The number of parallel threads that insert the record. Use multiple threads to emulate multiple concurrent clients. The number of milliseconds the application waits on each thread before sending two consecutive transaction insert requests. The number of seconds the test runs. This is the year of all transactions inserted by the program. All transactions start on January 1 st of the year with a second timespan. In this way the test transactions generated will be easily recognizable inside the database. Section Results Seconds elapsed Transactions inserted Transactions per second The actual duration of the test. The amount of transactions successfully processed in the predefined time. The average of transactions per second successfully processed in the predefined time. TCPOS The Stress Test tool Page 10/14

11 Database snapshot test tab This tab is used to test the requests executed by FrontEnd to the ServerService when downloading the local database used by tills. The result highlights how many concurrent snapshots can be handled and also the test load balancing feature given by the ServerService configuration. After filling the parameters, press the Start button to start the test. Field Dowloading tills Description The minimum and maximum number of concurrent downloads (tills) to be tested. If the number inserted in these fields is higher than the actual number of tills available in the environment, the program will adjust automatically the value. TCPOS The Stress Test tool Page 11/14

12 Get card data tab This tab is used to test the requests executed by FrontEnd to the ServerService when trying to retrieve data about customer cards read on tills. This test checks: the availability during a sample working day; the roundtrip during a sample working day; the Database/ServerService load during a sample working day. After filling the parameters, press the Start button to start the test. Field Card number Check Interval Description The number of the card that will be regularly checked. The interval in seconds between requests. TCPOS The Stress Test tool Page 12/14

13 Connections tab This tab is used to test the maximum amount of connections handled (software and hardware limits); it also checks the possible pending requests or discarded connections. After filling the parameters, press the Start button to start the test. Field Parallel threads Delay after request (ms) Description The amount of requests made using multiple threads to emulate multiple concurrent clients. The number of milliseconds that the application waits on each thread after the request has been made before closing the thread to emulate server side process time. Section Results Requests made Pending requests Requests terminated Request errors The amount of requests made during the test. The amount of requests still pending during the test. The amount of requests successfully terminated after the test. The amount of requests that have not been processed after the test. TCPOS The Stress Test tool Page 13/14

14 Shifts tab This tab is used to test the requests executed by FrontEnd to the ServerService when transmitting data related to shifts to the database. The result highlights how many shifts can be successfully processed in a predefined time and how many concurrent clients may be handled by the reviewed environment. After filling the parameters, press the Start button to start the test. Field Shifts file Parallel threads Delay between consecutive requests (ms) Execution seconds Shifts year Section Results Seconds elapsed Shifts inserted Shifts per second Description Select the file, generated by FrontEnd, containing the data of the shifts to be used as sample. The structure of this file corresponds to the one of the files usually generated by FrontEnd and stored in the local directory Frontend\LocalDB\OpenShifts.xml. Only a part of the shifts available in the sample file is used during the stress test. The number of parallel threads that insert the record. Use multiple threads to emulate multiple concurrent clients. The number of milliseconds the application waits on each thread before sending two consecutive requests. The number of seconds the test runs. This is the year of all shifts inserted by the program. All shifts start on January 1 st of the year with a second timespan and are closed. In this way the test shifts generated will be easily recognizable inside the database. The actual duration of the test. The amount of shifts successfully processed in the predefined time. The average of shifts per second successfully processed in the predefined time. TCPOS The Stress Test tool Page 14/14