Versions Compared

Old Version 6

changes.mady.by.user Chris Welford

Saved on

compared with

New Version Current

changes.mady.by.user Andy Humphries

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • PhixFlow Application Server - The PhixFlow application server is a Java-based application which runs within an Apache Tomcat container. PhixFlow supports installation on all the major hardware architectures and operating systems. Existing installations use Solaris, both Linux and Windows based servers.
  • Database Server - PhixFlow uses any major JDBC compliant database to store both configuration data and the results of analysis on data collected from other systems. Existing installations currently use either Oracle or Microsoft SQL Server

Please refer to Compatibility Guide and Upgrade Planning for infomation on supported databases and supported versions of versions Tomcat.

Figure 1 shows the most typical deployment of PhixFlow in which the application server and database server run on separate machines, however, for small proof of concept installations a single server may be used to host both the application and database servers.

...

The following are typical server sizes for small, medium and large installations. For large installations we recommend that you engage a PhixFlow consultant to verify requirements and analyse data volumes to be processed and retained within PhixFlow. Please note , that backup/recovery capacity is excluded in these sizing estimates.


 

Server Size

Small

Medium

Large

Daily records

10m

70m

200m

Application Server

CPU cores

4

12

24

Memory

16 GB

32 GB

64 GB

Disk space1

50 GB

100 GB

200 GB

Database Server

CPU cores

2

6

12

Memory

4 GB

8 GB

16 GB

Data disk space2

250 GB

2 TB

4 TB

Redo/Undo space

40 GB

400 GB

800 GB

...

Notes:

  1. The disk space on the

...

  1. application server is sized assuming that there may be files placed on the server disk for PhixFlow to read. If no files are to be placed on the application server (e.g. PhixFlow will read files from an

...

  1. external location) then only a small disk is required for the operating system and PhixFlow application software.

...


  2. Note that these figures indicate the amount of database disk storage required which scales with the amount of raw and result data configured to be retained by PhixFlow. Some implementations with a high number of daily records but which only maintain problematic data may require less space than this.

Database Server Disk Configuration

...

On linux a limit can be imposed on the number of open file descriptors a user can have. You can see the current limit by running the ulimit command:

Code Block
languagebashtext
> ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 3889
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 3889
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

...

Ensure that the user that will run tomcat has a limit of at least 50,000, or is unlimited. Although PhixFlow will generally open only a fraction of 50,000 file descriptors, it is best to ensure that this limit can never be hit reached, since otherwise numerous low level errors can occur.