SAP Omnichannel POS by GK

POS Client - Sizing Guide

Version: 5.5
Copyright

© SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose
without
the express permission of SAP SE. The information contained herein may be changed without
prior notice.

Some software products marketed by SAP SE and its distributors may contain proprietary software
components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE and its affiliated companies ("SAP Group") for
informational purposes only without representation or warranty of any kind, and SAP Group shall
not be liable for errors or omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE in Germany and in several other countries.

For more information on trademarks and copyrights, see http://www.sap.com

(http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark).
Typographic Conventions

For easier reading and better understanding, we will use in this documentation the following
typographic conventions and symbols.

Format Description

bold References to the screen display:

Words or characters quoted from the screen. This includes

field names, pushbutton names, menu names, masks,
menu paths and menu options.

Example: Select OK.

bold and italic Highlighting:

Highlighted words or expressions in the body text.

Example: Please always follow the instructions.

Proportional spacing bold Exact user input:

This includes words or characters that must be entered by

the user in the application exactly as indicated in the
documentation.

Example: Amount: 20.00 EUR.

CAPITAL LETTERS Names of keyboard keys:

Example: SHIFT, CTRL or ALT.

Contents
Contents

Introduction................................................................
................................................................................................
...................................................................................
................................................... 7

Architecture ................................................................
................................................................................................
...................................................................................
................................................... 8

Sizing: POS Fat Client ................................................................

................................................................................................
...................................................................
................................... 9
Basic configuration ................................................................
................................................................................................
................................................................................................
...........................................................................
........................................... 9
Assumptions ............................................................................................................................................................. 9
Minimum configuration ......................................................................................................................................... 9
Recommended configuration............................................................................................................................... 9

Scaling................................
Scaling................................................................
................................................................................................
................................................................................................
................................................................................................
.................................................................
................................. 9

Database size ................................................................

................................................................................................
................................................................................................
..................................................................................
.................................................. 10
Master data.............................................................................................................................................................10
Transaction data ....................................................................................................................................................10

RAM ................................................................
................................................................................................
................................................................................................
................................................................................................
...................................................................
................................... 10

Network ................................................................
................................................................................................
................................................................................................
............................................................................................
............................................................ 11

Reference environment
environment for sizing ................................................................
................................................................................................
................................................................................
................................................ 11
Influencing factors for sizing of the reference environment.......................................................................11
Sizing of the reference environment ................................................................................................................11
Performance of the reference environment...................................................................................................12

Test results ................................................................

................................................................................................
................................................................................................
......................................................................................
...................................................... 12

Sizing: POS Thin Client ................................................................

..............................................................................................
.............................................................. 13
Basic configuration ................................................................
................................................................................................
................................................................................................
.........................................................................
......................................... 13
Assumptions ...........................................................................................................................................................13
Minimum configuration .......................................................................................................................................13
Recommended configuration.............................................................................................................................13
Scaling................................
Scaling................................................................
................................................................................................
................................................................................................
...............................................................................................
............................................................... 13

Database size ................................................................

................................................................................................
................................................................................................
..................................................................................
.................................................. 14
RAM ..........................................................................................................................................................................14

Network ................................................................
................................................................................................
................................................................................................
............................................................................................
............................................................ 14

Reference environment for sizing ................................................................

................................................................................................
................................................................................
................................................ 14
Influencing factors for sizing of the reference environment.......................................................................14
Sizing of the reference environment ................................................................................................................15
Performance of the reference environment...................................................................................................15

Sizing: POS Service ................................................................

................................................................................................
....................................................................
.................................... 16
Sizing procedure ................................................................
................................................................................................
................................................................................................
.............................................................................
............................................. 16
Sizing checklist .......................................................................................................................................................16

Sizing of the
the application server ................................................................
................................................................................................
....................................................................................
.................................................... 16
Number of required application servers .........................................................................................................16
Influencing factors for sizing of the application servers...............................................................................17
Scaling ......................................................................................................................................................................18

Sizing of the database................................................................

................................................................................................
................................................................................................
....................................................................
.................................... 20

Reference environment for sizing ................................................................

................................................................................................
................................................................................
................................................ 21
Influencing factors for sizing of the reference environment.......................................................................21
Sizing of the reference environment ................................................................................................................22
Performance of the reference environment...................................................................................................23

Sizing: Smart POS Service ................................................................

........................................................................................
........................................................ 24
Sizing procedure ................................................................
................................................................................................
................................................................................................
.............................................................................
............................................. 24

Sizing of the application server ................................................................

................................................................................................
....................................................................................
.................................................... 24
Influencing factors for sizing of the application servers...............................................................................24
Scaling ......................................................................................................................................................................25

Reference environment for sizing ................................................................

................................................................................................
................................................................................
................................................ 26
Influencing factors for sizing of the reference environment.......................................................................27
List of Illustrations

Figure 1 POS Service Application Cluster [1] ..................................................................................................20

Introduction 7

Introduction

This document outlines the factors influencing the sizing of the following applications:

1. POS Thin Client

2. POS Fat Client
3. POS Service for POS Thin Clients
4. Smart POS Service

The document describes the requirements for RAM, CPU, hard disk, etc. in the different
deployment scenarios, and gives additional information on application scaling.

For information on the installation process, refer to the corresponding Installation Guide. For
information on the operation process, refer to the corresponding Operation Guide. For
information on updates from older versions, refer to the corresponding Upgrade and Update
Guide.
8 Architecture

Architecture

For architecture information, refer to the Architecture Master Guide.

Sizing: POS Fat Client 9

Sizing: POS Fat Client

Basic configuration

Assumptions
• Operating system is already installed. Indicated file system size refers to the portion
needed in addition to the operating system.
• Number of item master data records: 100,000 items
• Number of promotions 1,000
• No saving of customer data
• Number of transactions per day: 1,500 with an average of 10 line items
• Log file backup: 30 days
• Processor class: Intel Celeron processor

Minimum configuration
Type CPU RAM Hard disk

TouchPOS 2 GHz, Single Core 1 GB 3 GB

Recommended configuration
Type CPU RAM Hard disk

TouchPOS 2 GHz, Dual Core 2 GB 10 GB

Scaling

The table below shows the additional resources required per influencing factor. Values are based
on the minimum system requirements described under "Minimum configuration". The data volume
of the POS especially depends on the number of transactions per day and on the master data
(items, GTINs, merchandise categories, customers, promotions, etc.).

Factor Instance + CPU + RAM + Hard disk

Number of items 100,000 - 500,000 0.5 GHz 0 MB 1.0 GB

Number of items 500,000 - 2,500,000 1.0 GHz 512 MB 2.0 GB

Number of promotions 1,000 - 25,000 0.5 GHz 0 MB 0.5 GB

Number of customers 0 - 5,000 0 GHz 0 MB 0.25 GB

10 Sizing: POS Fat Client

Factor Instance + CPU + RAM + Hard disk

Number of customers 5,000 - 50,000 0 GHz 128 MB 0.5 GB

Number of transactions 1,500 - 3,000, 20 line items 0 GHz 0 MB 0.5 GB

Number of transactions 1,500 - 3,000, 40 line items 0 GHz 0 MB 1.0 GB

Number of transactions 3,000 - 5,000, 20 line items 0.5 GHz 0 MB 1.5 GB

Number of transactions 3,000 - 5,000, 40 line items 0.5 GHz 0 MB 2.0 GB

Master POS Infoserver running on a POS 0.5 GHz 128 MB 0.5 GB

Database size

Master data
Items DB size

30,000 140 MB

100,000 460 MB

500,000 2.3 GB

Transaction data
Transactions DB size

10,000, 10 line items 250 MB

10,000, 100 line items 2 GB

10,000, 500 line items 10 GB

RAM

Application Environment Heap Permanent size Typical footprint RAM required

TouchPOS 32 Bit OS, 32 Bit Java Runtime 300 MB 100 MB 800 MB 768 MB

TouchPOS 64 Bit OS, 64 Bit Java Runtime 350 MB 130 MB 900 MB 1 GB

The RAM requirements also depend on the used Java Runtime and the garbage collector. The data
refers to Oracle Java 1.8 with Concurrent Mark Sweep Garbage Collector.

Effects of other configurations:

• Java 1.7 instead of 1.8 (64 Bit): 50 MB less

Sizing: POS Fat Client 11

• G1 garbage collector instead of CMS: 50 MB more

Network

Application Connected to Network type Minimum Recommended

TouchPOS Central POS Server, Store Device Control WAN 256 KBit 1024 KBit

Central Services WAN 256 KBit 1024 KBit

Reference environment for sizing

The reference environment is meant to represent a typical configuration for the live operation, and
is used for the internal performance tests. Specific assumptions are made resulting in a defined
sizing.
The test results are an indicator of the performance that can be achieved under these conditions.

Influencing factors for sizing of the reference environment

Assumptions for influencing factors

Influencing factor Instance

Number of items 50,000

Graphical customer display No

Platform
Criterion Instance

Operating system Windows

Runtime Oracle Java Runtime 8 (JRE)

Database Derby (embedded Java)

POS type TouchPOS

Sizing of the reference environment

Criterion Instance

POS model Wincor Beetle M-II plus

POS type TouchPOS

Operating system POS Ready 2009

12 Sizing: POS Fat Client

Criterion Instance

CPU Intel Core 2 Duo 2.8 GHz

RAM 2 GB

Hard disk 500 GB, 7200 rpm

Network 100 MBit

Performance of the reference environment

Test results

Criterion Result

Item entry max.: 400 ms, average: 300ms

POS Client start 2min

First login (without EFT) 7s

Sizing: POS Thin Client 13

Sizing: POS Thin Client

Basic configuration

Assumptions
• Operating system is already installed. Indicated file system size refers to the portion
needed in addition to the operating system.
• Number of item master data records: 100,000 items (stored in the central POS Service)
• Number of promotions 1,000 (stored in the central POS Service)
• No saving of customer data
• Number of transactions per day: 1,500 with an average of 10 line items
• Log file backup: 30 days
• Processor class: Intel Celeron processor

Minimum configuration
Type CPU RAM Hard disk

TouchPOS 1 GHz, Single Core 1 GB 3 GB

Recommended configuration
Type CPU RAM Hard disk

TouchPOS 2 GHz, Dual Core 2 GB 10 GB

Scaling

The table below shows the additional resources required per influencing factor. Values are based
on the minimum system requirements described under "Minimum configuration".

Factor Instance + CPU + RAM + Hard disk

Number of promotions 1,000 - 25,000 0.5 GHz 0 MB 0 GB

Number of transactions 3,000 - 5,000, 20 line items 0.5 GHz 0 MB 0 GB

Number of transactions 3,000 - 5,000, 40 line items 0.5 GHz 0 MB 0 GB

Master POS Infoserver running on a POS 0.5 GHz 128 MB 0.5 GB

14 Sizing: POS Thin Client

Database size

The POS Thin Client does not have a local database.

RAM
Application Environment Heap Permanent size Typical footprint RAM required

TouchPOS 32 Bit OS, 32 Bit Java Runtime 230 MB 50 MB 400MB 512 MB

TouchPOS 64 Bit OS, 64 Bit Java Runtime 260 MB 80 MB 550 MB 768 MB

The RAM requirements also depend on the used Java Runtime and the garbage collector. The data
refers to Oracle Java 1.8 with Concurrent Mark Sweep Garbage Collector.

Effects of other configurations:

• Java 1.7 instead of 1.8 (64 Bit): 50 MB less

• G1 garbage collector instead of CMS: 50 MB more

Network

Application Connected to Network Minimum Recommended Comment

type

TouchPOS Central POS WAN 256 KBit 1024 KBit

Server

POS Service WAN 1024 KBit 2048 KBit Required bandwidth depends on the number of
POS Clients in the store.

Central Services WAN 256 KBit 1024 KBit Required bandwidth depends on the number of
POS Clients in the store.

Reference environment for sizing

The reference environment is meant to represent a typical configuration for the live operation, and
is used for the internal performance tests. Specific assumptions are made resulting in a defined
sizing.

The test results are an indicator of the performance that can be achieved under these conditions.

Influencing factors for sizing of the reference environment

Assumptions for influencing factors

Influencing factor Instance

Number of items 50,000

Sizing: POS Thin Client 15

Influencing factor Instance

Graphical customer display No

Platform
Criterion Instance

Operating system Windows

Runtime Oracle Java Runtime 8 (JRE)

Database Derby (embedded Java)

POS type TouchPOS

Sizing of the reference environment

Criterion Instance

POS model Wincor Beetle M-II plus

POS type TouchPOS

Operating system POS Ready 2009

CPU Intel Core 2 Duo 2.8 GHz

RAM 2 GB

Hard disk 500 GB, 7200 rpm

Network 100 MBit

Performance of the reference environment

Criterion Instance

Item entry max.: 500 ms, average: 350 ms

POS Client start 2min

First login (without EFT) 8s

16 Sizing: POS Service

Sizing: POS Service

Sizing procedure

Sizing of the POS Service depends on several factors. It is recommended to proceed as follows:

• Use sizing checklist to determine the relevant influencing factors (countries, stores,
platform)
• Sizing of application server instances or cluster
• Calculation of the database sizes
• Sizing of database server instances or cluster

Sizing checklist
The standard sizing checklist for POS Service contains important key figures, which are required to
determine the sizes of application and database servers. Among others, the following key figures
are required:

• Platform (operating system, application server)

• Database
• Number of countries, stores and POS Clients
• Average values for transactions per day, number of line items, etc.

Sizing of the application server

Number of required application servers

Multiple servers due to higher load

One POS Service instance (= node) in an application server is able to respond to a defined number
of POS Thin Client requests. If one instance is not enough, several instances can be integrated in a
cluster.

In this case, a load balancer will be placed in front of the cluster. It is essential that the load
balancer supports the sticky session mode. This means that the load balancer, during a session,
will always send the requests from one Thin Client to the same node unless the node fails. If the
node fails, the call will be routed to another node.

Generally, each temporary state of a transaction is persisted in the database and kept in the main
memory during the session. Only if a change between nodes occurs, the POS transaction will be
reloaded and added again to the session. In all the remaining cases, the transaction from the main
memory will be used.
Sizing: POS Service 17

Different versions requiring different application servers

One application server or cluster is able to simultaneously run one version of the POS Service
application only. In case of different countries, it must be checked if it is possible to use the same
version with different, country-specific configurations. If this is not possible, it will be necessary to
use different separate application servers (i.e. countries) for the different versions.

However, one POS Service instance may have:

• POS Clients/stores in different time zones, independently of the server time zone.
• Different master data sets for each of the stores or countries.
• Different configurations for each of the stores or countries.

Due to the one software version restriction, special attention should be paid to countries where
fiscalization is required. Depending on the applicable fiscalization laws, certification may be
required for new versions in these countries. Generally, this will result in lower update frequencies
and own versions for the concerned countries.

Influencing factors for sizing of the application servers

Overview
The following functional use cases are relevant for sizing of the POS Service:

• Number of simultaneous accesses to the POS Thin Client

• Complexity of price calculation

Technical factors:

• Used runtime: Apache Tomcat (with Oracle JDK 8) versus SAP NetWeaver (with SAP JDK 6)

Simultaneous accesses
The POS Service uses the business layer of the POS application. Thus, the POS Thin Clients will call
the POS Service for each process step.
During usual POS Client operation, the majority of requests refer to:

• Item entry (including price calculation)

• Tender entry
• Opening a transaction
• Subtotal
• Closing a transaction

The frequency of item entry and transaction closing should be taken into account for sizing of the
POS Service. These values depend on the average number of transactions per day for all the
stores, and on the average number of line items per receipt.
18 Sizing: POS Service

If the peak is considerably higher than the average values, peak values should be used for sizing
instead. If the difference between peak and average values is not extremely large, you can cope
with a buffer.

Complex price calculations

Price calculation is performed for each item entry (or change of receipt line items). It depends on
several factors how much time is needed for calculation:

• Number of receipt line items

• Number of promotions applicable in the receipt

If there are few promotions only, price calculation is done very quickly. However, if there are a lot
of applicable promotions and a high number of receipt line items, price calculation may be decisive
for runtime duration of item entry. In this case, master data lookup and business logic will be of
less importance.

Platform and runtime

Application server
Using SAP NetWeaver as the runtime environment offers a large number of operational benefits
with respect to clustering and monitoring. Requirements of resources, however, are lower with
Tomcat. Using Windows or Linux as the operating system does not affect the sizing at all.

Apache Tomcat Application Server currently does not yet support clustering.

Database
It is recommended to not virtualize the database server as it depends on a good I/O performance
to a large extent.

It is recommended to use Oracle as the database server, and Oracle Real Application Server (RAC)
for larger installations.

Scaling

Influencing factors and and their effects

Factor Instance + CPU App + RAM App + CPU DB + RAM DB
Server Server Server Server

Operating system Linux + 0% + 0% + 0% + 0%

Application server Tomcat - 30% - 6 GB + 0% + 0%

Number of items < 1,000,000 per + 0% + 0% + 25% + 25%

store
Sizing: POS Service 19

Factor Instance + CPU App + RAM App + CPU DB + RAM DB

Server Server Server Server

Number of promotions < 1,000 + 25% + 0% + 0% + 0%

Number of promotions < 10,000 + 50% + 0% + 0% + 0%

Number of receipt line 10-20 + 25% + 10% + 20% + 10%

items

Number of receipt line 20-40 + 50% + 20% + 40% + 20%

items

Number of item entries Linear Linear Linear Linear

In general, scaling of the POS Service is almost linear with respect to the number of simultaneous
item entries. Server sizes should be calculated with a certain buffer, i.e. peak condition should not
correspond to 100% server load. If the server scaling is not sufficient, cluster operation mode will
be required.

Cluster operation mode

Apache Tomcat Application Server currently does not yet support clustering.

Load balancer
If the SAP NetWeaver Application Server runs in a cluster, a load balancer will be placed in front of
the cluster. Depending on the load balancer, allocated CPU resources should be increased by 10-
20%. In case of the SAP Web Dispatcher e.g., increase by 20%.

Cluster structure
A NetWeaver cluster consists of several NetWeaver nodes. A NetWeaver node can run on different
hardware or different virtual machines.
A load balancer will be placed in front of the cluster (e.g. SAP Web Dispatcher), distributing the
requests to the NetWeaver nodes. For synchronization of the nodes, GK uses an own cluster
framework, which is able to directly cooperate with NetWeaver mechanisms. In addition, the
framework distributes tasks to various nodes.

Multiple NetWeaver Server processes can be executed in one NetWeaver node. Each of these
processes uses its own Java Virtual Machine (JVM), which is separated from the others. On the one
hand, this allows compensating the possible failure of a JVM. On the other hand, better hardware
utilization is provided in case of several processes running on accordingly sized NetWeaver
machines (i.e. large number of CPUs and a lot of RAM). SAP ICM (Internet Communication
Manager) is used to distribute the requests to several NetWeaver Server processes.
20 Sizing: POS Service

Figure 1 POS Service Application Cluster [1]

Important notes:
• The POS Service does not use an Enterprise
Enterprise Scheduler. The Enterprise Scheduler is used if
both a POS Service and a POS Server are running in the same application. The scheduler is
responsible for distributing and synchronizing the tasks within the cluster.
• All the nodes logically access the same database. It is even possible to use a database cluster
(e.g. Oracle RAC)

NetWeaver
It is recommended to use one NetWeaver Server process for approx. 8 CPUs with 8 to 12 GB RAM.

Sizing of the database

For the POS Service, this depends on:

1. Saving of transactions: The transactions are saved to the POS Server transaction pool. For
database sizing, refer to the POS Server Sizing Guide.
2. Master data reading: Master data is loaded via Store Device Control. The size of the
database depends on the number
n of master data. Refer to the Store Device Control Sizing
Guide.
Sizing: POS Service 21

3. General performance of POS Service accesses

The general performance depends on the number of simultaneous accesses by POS Clients. The
number of simultaneous item scans per second is relevant for the sizing. As other types of
accesses, e.g. subtotal, payment etc. behave in a similar way, the number of item scans can be
used as the key figure for sizing.

The sizing results from the measured values:

Database CPU RAM

Oracle 12g 12 CPU 40 GB

Used transactions:

• 10 receipt line items per receipt

• 1 promotion per receipt

Measurement results:

Item scans per second DB server load

200 8%

330 12%

500 20%

690 27%

Reference environment for sizing

The reference environment is meant to represent a typical configuration for the live operation, and
is used for the internal performance tests. Specific assumptions are made resulting in a defined
sizing.
The test results are an indicator of the performance that can be achieved under these conditions.

Influencing factors for sizing of the reference environment

Assumptions for influencing factors

Influencing factor Instance

Simultaneous accesses 400 scans per second

Complex price calculations Average: 1 promotion per receipt

Master data 30,000 items

22 Sizing: POS Service

Influencing factor Instance

Receipt line items 10

Promotions 100

Platform
Criterion Instance

Operating system Linux

Application server SAP NetWeaver

Database Oracle

Clustering Yes (with and without the SAP Web Dispatcher as load balancer)

Sizing of the reference environment

Application server
Criterion Instance

Operating system SUSE Linux Enterprise 11 SP3

Application server SAP NetWeaver 7.40

CPU Intel Xeon E5-2648L, 1.80 GHz, 4 CPUs

RAM 24 GB RAM

Nodes 1-4

Load balancer SAP Web Dispatcher

NetWeaver Server processes 1

Database
Criterion Instance

Operating system SUSE Linux Enterprise 11 SP3

Database Oracle 12.1g

CPU Intel Xeon CPU E5-2630 v2, 2.6 GHz, 12 cores

RAM 56 GB RAM
Sizing: POS Service 23

Performance of the reference environment

Scenario Avg. processing time Scans per second CPU usage [%]

Enter item Subtotal Payment Application server Database

1x NetWeaver node 378.3927 328.9477 323.5744 201.21 91.42 7.58

2x NetWeaver node 441.6726 389.0743 381.3337 332.23 90.09 11.50

3x NetWeaver node 414.612 379.2275 349.7044 504.20 91.38 18.07

4x NetWeaver node 414.0674 367.6985 355.8857 698.08 92.40 26.17

4x NetWeaver node + Web Dispatcher 424.6555 413.5979 346.7171 618.24 89.32 24.00
24 Sizing: Smart POS Service

Sizing: Smart POS Service

Sizing procedure

The Smart POS Service is a POS Service that is locally installed in the store. If the central POS
Service fails, all of its services will be assumed by the Smart POS Service, for all the POS Thin Clients
of the store.

Sizing of the application server

Influencing factors for sizing of the application servers

Overview
The following functional use cases are relevant for sizing of the POS Service as a Smart POS:

• Number of simultaneous accesses to the POS Thin Client in the store

• Complexity of price calculation

Technical factors:

• Platform: Used database

Simultaneous accesses
The POS Service running as a Smart POS uses the business layer of the POS application. Thus, the
POS Thin Clients will call the POS Service for each process step.
During usual POS Client operation, the majority of requests refer to:

• Item entry (including price calculation)

• Tender entry
• Opening a transaction
• Subtotal
• Closing a transaction

The sizing of the Smart POS Service should be determined according to the frequency of item
entries and transaction closing. These values depend on the average number of transactions per
day for all the stores, and on the average number of line items per receipt.

If the peak is considerably higher than the average values, peak values should be used for sizing
instead. If the difference between peak and average values is not extremely large, you can cope
with a buffer.
Sizing: Smart POS Service 25

Complex price calculations

Price calculation is performed for each item entry (or change of receipt line items). It depends on
several factors how much time is needed for calculation:

• Number of receipt line items

• Number of promotions applicable in the receipt

If there are few promotions only, price calculation is done very quickly. However, if there are a lot
of applicable promotions and a high number of receipt line items, price calculation may be decisive
for runtime duration of item entry. In this case, master data lookup and business logic will be of
less importance.

Platform and runtime

Application server
Currently, the store supports Apache Tomcat Application Server only. Clustering is not supported
with the Smart POS.

Database

The following variants exist:

• Embedded database: Derby

• Oracle Express
• Oracle

Scaling

Influencing factors and and their effects

Factor Instance + CPU App + RAM App + CPU DB + RAM DB
Server Server Server Server

Operating system Linux + 0% + 0% + 0% + 0%

Number of items < 1,000,000 per + 0% + 0% + 25% + 25%

store

Number of promotions < 1,000 + 25% + 0% + 0% + 0%

Number of promotions < 10,000 + 50% + 0% + 0% + 0%

Number of receipt line 10-20 + 25% + 10% + 20% + 10%

items

Number of receipt line 20-40 + 50% + 20% + 40% + 20%

items

Number of item entries Linear Linear Linear Linear

26 Sizing: Smart POS Service

In general, scaling of the POS Service is almost linear with respect to the number of simultaneous
item entries. Server sizes should be calculated with a certain buffer, i.e. peak condition should not
correspond to 100% server load.

Sizing of the database

For the Smart POS Service, this depends on:

1. Saving of transactions: The transactions are saved to the POS Server transaction pool. For
database sizing, refer to the POS Server Sizing Guide.
2. Master data reading: Master data is loaded via Store Device Control. The size of the
database depends on the number of master data. Refer to the Store Device Control Sizing
Guide.
3. General performance of POS Service accesses

The general performance depends on the number of simultaneous accesses by POS Clients. The
number of simultaneous item scans per second is relevant for the sizing. As other types of
accesses, e.g. subtotal, payment etc. behave in a similar way, the number of item scans can be
used as the key figure for sizing.

The sizing results from the measured values:

Application server and database CPU RAM

Tomcat and Oracle XE/Oracle/Derby 4 CPU 8 GB

Used transactions:

• 10 receipt line items per receipt

Measurement results:

Database Max. number of POS Thin Client requests per second

Derby 5

Oracle Express 120

Oracle Depends on RAM/CPU

If Derby is used, the number of clients is severely reduced. Oracle Express variant is limited due to
CPU and RAM usage by the Express version.
A higher number of client accesses is possible with unlimited Oracle Database.

Reference environment for sizing

The reference environment is meant to represent a typical configuration for the live operation, and
is used for the internal performance tests. Specific assumptions are made resulting in a defined
Sizing: Smart POS Service 27

sizing.
The test results are an indicator of the performance that can be achieved under these conditions.

Influencing factors for sizing of the reference environment

Assumptions for influencing factors

Influencing factor Instance

Master data 100,000 items

Receipt line items 10

Platform
Criterion Instance

Operating system Linux

Application server Tomcat

Database Oracle, Oracle XE, Derby

Application server and database

Criterion Instance

Operating system SUSE Linux Enterprise 11 SP3

Application server Tomcat 7

Database Oracle 12.1, Oracle 11 XE, Derby 10

CPU Intel Xeon E5-2648L, 1.80 GHz, 4 CPUs

RAM 8 GB RAM

Performance of the reference environment

Database Max. number of POS Thin Client requests per second CPU load RAM load

Derby 5 82 % 1.2 GB

Oracle Express 120 85 % 3.6 GB

Oracle Depends on RAM/CPU

Contact

GK SOFTWARE AG
Waldstraße 7
08261 Schöneck

Germany
Tel.: +49 (0) 3 74 64 84 – 0
Fax : +49 (0) 3 74 64 84 - 15

E-mail: documentation@gk-software.com
www.gk-software.com