Impact of application server resources
The first step toward a performant Bravura Security Fabric instance is to provision all production application servers according to the installation Server requirements .
The following server resources are important:
Multi-CPU (the more CPUs and faster, the more binaries can run at the same time).
Disk I/O is crucial for the application server. Services cache most files they need as they start up, but a large part of the automation in the application will use some sort of scripting in Python and components, which are all loaded on demand. Low disk latency (imposed by network conditions at the data center) can easily slow down any automated process, especially when millions of records are read from list databases.
RAM is important from its absolute minimum of 4GB to an acceptable value of 8GB, available to leave space for troubleshooting tools to run when needed.
In the current version, RAM use will peak during
psupdateand skin generation (node.exe will grow to 1.2GB as it compiles the various Angular apps that make up the web-based interface).Under high use ( 60-100 users per node simultaneously), the Ajax service can grow to 2GB or more.
The more concurrent agents are to be run from the primary or from a proxy server, the more RAM will be needed.
Starting with Bravura Security Fabric version 12, list files from target systems are SQLite databases instead of structured text files, which will increase the listing and filtering performance, at the expense of more RAM use per agent, for the
iddiscoverservice, and for any other process that handles list files.