Changes

Bxp Infrastructure Capacity

97 bytes added, 16:23, 11 February 2021

no edit summary

= Background Methodology Used =

Please note that this planning was confirmed in February 2016. In March 2016 bxp Release 10 saw a significant increase in server performance. bxp has not been tested against the improved server capacities but will exceed all figures currently stated. [[Bxp_Release_10]]

 Capacity planning is essential to ensure that performance of the solution is effective for all scenarios. Given the extremely heterogeneous nature of the BE bxp environment it becomes “best guess” for items that are being prototyped.

Table 2. Cisco ASA 5510 Adaptive Security Appliance Platform Capabilities and Capacities

Feature Description  

Firewall Throughput

* Up to 300 Mbps

 

=== Servers ===

 

 

==== Overview ====

 

Supplied on application via Business Development manager

= Testing Profiles =

==== Asset Register ====

 

 

 

= Testing approach =

The user profile within BE bxp varies from client to client and system to system, making creating an example user profile an almost impossible task. So instead we have three possible ways of reviewing the capacity.

Putting a heartbeat on the system to keep an eye on when the system was available is currently done by All n One and Sungard ASwill get immediate alerts from AWS if the servers reach any kind of storage or usage capacity that could cause a slowdown or make the service unavailable. It The service is monitored 24/7 and any notification of a ping test fault affecting availability will be issued to ensure the system responds. This has been 100% since October 2008bxp immediately. This doesn’t really provide capacity planning but to state that the service was available.

When performing the test, we need to ensure consistency. For this certain elements may be ruled in or out. The key timing aspects are:

 

Chronological positioning

* Month of year

* Known project events

 

Testing environment

* Load on internet connection / dedication of internet connection

* Running applications

* Interim connections (communications devices / hops between testing machine and BEbxp) 

Request

 

 

= Potential worked models =

Here is a snaphot of Web 1 (on the right) and the Database server (on the left) at 12:25 pm 3rd March 2014. This is billing day / end of month, with a full Live operational load and a virus scan being performed. At this point you can see the spikes of monthly reports being generated displays supplied on the database server with no operational slow downapplication via Business Development manager.

 

== Worked Example 1: - External site usage and uploading ==

Remote server upload speed: Unknown, assume unlimited.BE server accept speed: Bottleneck = Firewall 300MbpsFile size: 500Kb

bxp server accept speed: Bottleneck = Firewall 300Mbps

File size: 500Kb  Result: BE could bxp at this level theoretically accept accepts 600 documents in 1 second with no other traffic or activity.

This means BE bxp can handle 600,000 requests per second for pages simultaneously.

Using the BEAPI, XML responses are sent. The XML with some data would not typically be much bigger. With a conservative guesstimate of 2Kb, we can guesstimate that BE bxp can supply 150,000 responses per second.   [[Category:Topic:About bxp]][[Category:Topic:Security]]

• ← Older edit

meabh.landers@allnone.ie

240

edits