Bandwidth utilization can be difficult to estimate because usage of the “On” products varies from one school to the next.

One way to estimate is by taking a look at aggregate bandwidth utilization from the back-end (during peak times) and averaging out over all Clients.  This approach indicates an additional 1 Mbps of bandwidth will be needed to run the “On” products.  Blackbaud recommends an additional 5 to 10 Mbps to provide enough headroom to handle individual spikes at your school.  In our experience school’s that have added 5 to 10 Mbps have been the most pleased with the performance of the “On” products. 

It is also possible to estimate bandwidth requirements by looking at information on what is required for a single user to load and run the application.  The tables below include detailed information on loading the application, both initially, and from cache.  These numbers can be used in conjunction with anticipated usage from campus to come up with the estimated bandwidth impact.

Initial load (not cached) of common “On” product screens

Request

# Objects

Bytes Sent

Bytes Received

Login Screen

29

17,393

289,190

App Load

87

73,803

1,871,194

onRecord Dashboard

47

57,465

125,177

 

Subsequent visit load (cached in user browser) of common “On” product screens*

Request

# Objects

Bytes Sent

Bytes Received

Login Screen

4

3,485

4,899

App Load

21

25,614

31,332

onRecord Dashboard

32

28,918

78,903

Capture of a single user continuously clicking through the Faculty Persona

Faculty Continuous Browsing for 1 min

351

426,869

2,331,015

 
 
Note: Releases occur once a week, typically on Wednesday’s, and often require users to download new versions of the source.