Bxp Infrastructure Capacity - Revision history

Meabh Landers at 15:23, 11 February 2021

2021-02-11T15:23:50Z

Philip Lacey: /* Servers */

2018-01-26T08:37:46Z

‎Servers

Philip Lacey: /* Testing approach */

2018-01-26T08:36:28Z

‎Testing approach

Philip Lacey: /* Background */

2018-01-26T08:35:49Z

‎Background

Philip Lacey: /* Background */

2018-01-26T08:35:10Z

‎Background

Philip Lacey at 08:34, 26 January 2018

2018-01-26T08:34:42Z

Philip Lacey: Philip Lacey moved page Business Express Infrastructure Capacity to Bxp Infrastructure Capacity

2015-04-20T17:02:47Z

Philip Lacey moved page Business Express Infrastructure Capacity to Bxp Infrastructure Capacity

Philip Lacey at 20:59, 9 November 2014

2014-11-09T20:59:52Z

Philip Lacey at 19:19, 9 November 2014

2014-11-09T19:19:42Z

Philip Lacey at 13:59, 7 August 2014

2014-08-07T13:59:15Z

← Older revision		Revision as of 15:23, 11 February 2021
Line 114:		Line 114:


−	~~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 AS~~. It is a ~~ping test~~ to ~~ensure the system responds. This has been 100% since October 2008~~. This doesn’t really provide capacity planning but to state that the service was available.	+	All n One will 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. The service is monitored 24/7 and any notification of a fault affecting availability will be issued to bxp immediately. This doesn’t really provide capacity planning but to state that the service was available.

@@ Line 96: / Line 96: @@
 === Servers ===
 Supplied on application via Business Development manager
 = Testing Profiles =

@@ Line 106: / Line 106: @@
 ==== Asset Register ====
-= Testing approach =
+= Testing Profiles =
@@ Line 164: / Line 164: @@
 = Potential worked models =

← Older revision		Revision as of 08:35, 26 January 2018
Line 1:		Line 1:
−	= ~~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]]		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]]

@@ Line 1: / Line 1: @@
 = Background =
-  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.
+  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]]
@@ Line 105: / Line 105: @@
 ==== Asset Register ====
 = Testing approach =

@@ Line 1: / Line 1: @@
 = Background =
-Capacity planning is essential to ensure that performance of the solution is effective for all scenarios.  Given the extremely heterogeneous nature of the BE environment it becomes “best guess” for items that are being prototyped.
@@ Line 108: / Line 110: @@
-The user profile within BE 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.
+The user profile within 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.
@@ Line 150: / Line 152: @@
 * Load on internet connection / dedication of internet connection
 * Running applications
-* Interim connections (communications devices / hops between testing machine and BE)
+* Interim connections (communications devices / hops between testing machine and bxp)
@@ Line 192: / Line 194: @@
 Remote server upload speed: Unknown, assume unlimited.
-BE server accept speed: Bottleneck = Firewall 300Mbps
+bxp server accept speed: Bottleneck = Firewall 300Mbps
 File size: 500Kb
-Result: BE at this level theoretically accepts 600 documents in 1 second with no other traffic or activity.
+Result: bxp at this level theoretically accepts 600 documents in 1 second with no other traffic or activity.
@@ Line 209: / Line 211: @@
-This means BE can handle 600,000 requests per second for pages simultaneously.
+This means bxp can handle 600,000 requests per second for pages simultaneously.
@@ Line 215: / Line 217: @@
-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 can supply 150,000 responses per second.
+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 bxp can supply 150,000 responses per second.

← Older revision	Revision as of 17:02, 20 April 2015
(No difference)

← Older revision		Revision as of 20:59, 9 November 2014
Line 221:		Line 221:
	[[Category:Topic:About bxp]]		[[Category:Topic:About bxp]]
	[[Category:Topic:Security]]		[[Category:Topic:Security]]
−	~~[[Category:FAQs]]~~

← Older revision		Revision as of 19:19, 9 November 2014
Line 216:		Line 216:

	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 can supply 150,000 responses per second.		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 can supply 150,000 responses per second.
		+
		+
		+
		+	[[Category:Topic:About bxp]]
		+	[[Category:Topic:Security]]
		+	[[Category:FAQs]]

@@ Line 178: / Line 178: @@
-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 operational load and a virus scan being performed.  At this point you can see the spikes of monthly reports being generated on the database server with no operational slow down.
+Live operational displays supplied on application via Business Development manager.
@@ Line 190: / Line 190: @@
-Remote server upload speed: 	Unknown, assume unlimited.
+Remote server upload speed: Unknown, assume unlimited.
-Result: BE could theoretically accept 600 documents in 1 second with no other traffic or activity.
+File size: 500Kb