Professional Documents
Culture Documents
uniFLOW Hardware Scoping - V1.0
uniFLOW Hardware Scoping - V1.0
uniFLOW Hardware Scoping - V1.0
Version 1.0
24-Sep-2014
Version 5.x
Technologies
uniFLOW, RPS, SPS
concerned
Short Summary This document should be utilized in order to scope/plan the uniFLOW infrastructure
within the customer environment.
These recommendations should act as guidelines and are subject to change in case of new
uniFLOW software/hardware releases.
Document Version Topic(s) Changes
changes
PLEASE NOTE: Serious problems might occur if you modify the registry of your Windows operating system incorrectly.
These problems might require that you reinstall the operating system. We strongly recommend to always back up the
registry of your Windows operating system before applying changes to it, just in case you do something wrong.
NT-ware does not assume any responsibility or liability for any impact on the operating system after changing the
Registry. You understand and accept that you use this information and modify the registry of your Windows operating
system at your own risk.
Pictograms
Important note: Information that is crucial for the correct functioning of the uniFLOW
software.
External manual: Pointer to additional manuals for third party hardware or third party
software.
Region Specific Feature: In case some features of uniFLOW are not universally
available, this icon will indicate it.
Contents
1 Introduction ............................................................................................... 1
2 Disclaimer .................................................................................................. 1
I
Confidentiality: Internal + Partner (R3P)
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
1 Introduction
Intention of this document:
This document should be utilized in order to scope/plan the uniFLOW infrastructure
within the customer environment.
These recommendations should act as guidelines and are subject to change in case of
new uniFLOW software/hardware releases.
2 Disclaimer
This guide offers an approximation of the hardware resources required to deploy
uniFLOW at your customer. Hardware sizing depends on many factors like the
complexity of the solution and the project requirements. This guide helps you to find
out what the hardware needs for your uniFLOW solutions are and/or to find an upper
and lower estimate for the hardware requirements.
Please be aware that benchmark and test results are taken within the NT-ware
in-house environment. Results in customer “live” environments may vary and show
different results.
Scanning tests are based on the I.R.I.S. engine IDRS 14.
If use cases are not covered within this document please get in touch with the NT-ware
Project Team via ITS (MOMPS Area) in order to receive further assistance regarding
hardware sizing recommendations.
1
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
2
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
3.2 Printing/Copying
Maximum amount of devices per server depending on uniFLOW features utilized
In environments where Remote Print Servers (RPS) are in use, NT-ware recommends to
utilize the main uniFLOW Server as “Application Server” only and to have all printers
connected/monitored by Remote Print Servers (RPS). This, on the one hand, makes it
easier to scale and maintain the uniFLOW environment and on the other hand
removes the dependency on the uniFLOW database (SQL Server) as the RPS can work
independent of the uniFLOW Server.
3
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
The numbers provided in the following table can be utilized as a guideline in order to
calculate the usage.
Please keep in mind that the “Database Format” “Standard (optimized for size)” is only
affecting the ServiceUsage_T table. Please check the uniFLOW User Manual for further
information.
uniFLOW can be installed with a “free of charge” Microsoft SQL Express Server. In
some cases a full SQL Server is required though. NT-ware recommends to install a full
SQL Server on a separate server.
For the “free of charge option” uniFLOW utilizes MS SQL 2008 R2 Express. This
database server is limited to the following maximums:
1 CPU
1 GB RAM (limited to 384 MB by uniFLOW installer)
10 GB Database size
4
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
If these limitations are not suitable for the planned uniFLOW installation then a full MS
SQL Server is required.
Having a full SQL Server running on the same server as uniFLOW is not recommended
by NT-ware due to the following reasons:
The SQL Server is very resource hungry and will take a huge amount of CPU
time.
I/O load is quite high depending on what is utilized within uniFLOW.
The memory footprint can be very large depending on configuration.
If a full SQL Server is already in place the uniFLOW database can be implemented
within the standard instance or within a new instance.
If implemented as a new SQL instance you will have the following advantages:
Memory can be specifically allocated to this instance (performance).
Specific configuration settings can be done e.g. security on user management
(security/maintenance).
the SQL instance will run on its own port so firewall rules can be set (security).
5
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
3.5 Scanning
Color Mode: Color Document processing 6000 pages /h 3300 pages /h 1600 pages /h
PDF 1.7 conversion (Parallel)
IHQC Level 3 compression
Time to process one 78 seconds 78 seconds 78 seconds
OCR (English)
test document
300 DPI
Color Mode: Grey scale Document processing 7000 pages /h 4000 pages /h 2100 pages /h
PDF 1.7 conversion (Parallel)
IHQC Level 3 compression
Time to process one 62 seconds 62 seconds 62 seconds
OCR (English) test document
300 DPI
Color Mode: Color Document processing 21000 pages /h 19000 pages /h 10000 pages /h
(Parallel)
PDF A conversion
No compression Time to process one 12 seconds 12 seconds 12 seconds
No OCR test document
300 DPI
In order to equip the server with hardware that fits the needs of the customers
workflows the table above shows benchmark results from low, medium and high
resource consuming scenarios.
The storage into different systems - like SharePoint, Scan to E-Mail, Therefore, etc. - is
not relevant for these tests and hardware scoping of the Scan Processing Server.
6
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
Processing of eight documents containing 20 pages each (160 pages in total) will be
faster due to the parallel processing than one document containing 160 pages.
7
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
Devices per Server, based on processing time in seconds and device utilization
10% 92 MFP 46 MFP 23 MFP 184 MFP 92 MFP 46 MFP 250 MFP 153 MFP 76 MFP
25% 36 MFP 18 MFP 9 MFP 73 MFP 36 MFP 18 MFP 123 MFP 61 MFP 30 MFP
50% 18 MFP 9 MFP 4 MFP 36 MFP 18 MFP 9 MFP 61 MFP 30 MFP 15 MFP
75% 12 MFP 6 MFP 3 MFP 24 MFP 12 MFP 6 MFP 41 MFP 20 MFP 10 MFP
*”Max processing time to finish job” is the time to finish the processing of one scan job. We are
taking the highest resource consuming scenario of the “Benchmark Test” into account utilizing
the “Standard Document”.
Example:
Customer requirements:
Jobs shall be processed within 3 Minutes
(180 seconds) after the job has been
scanned.
Device utilization within the company will
be about 25%.
8
Confidentiality: Internal + Partner (R3P)
White Paper uniFLOW Hardware Scoping
Example:
Customer requirements:
The customer has 30 devices .
Device utilization is at approx. 50% .
9
Confidentiality: Internal + Partner (R3P)