|
|
|
|
OverviewAll
8e6 R3000 filter sizing based on "concurrent user activity" (ie. active
web users on network). In addition, the basic assumption is all
standard R3000 filtering features are enabled -- ie. Invisible mode,
Proxy Pattern Blocking, P2P/IM filtering, HTTPS Filtering at Medium
(default), some authentication, etc.
Scaling
| Concurrent Users (web) |
8e6 R3000 model
|
Comments
|
| under 3k users |
R3000-MSA |
|
| 3-5k users |
R3000-G |
|
| 5-10k users |
R3000-S |
|
| over 10k users |
R3000-H |
|
| over 20k users |
R3000-H |
multiple model "H" units with SLB configuration (ie. leverage TopLayer IDS load balancer) |
Caveats
- All scaling subject to change at any time (but need mark in sand for today's customers doing renewals).
- keep it simple (all features enabled). We can't get into auth vs IPgroup vs P2P/IM off, etc
- only concurrent web users is important for
scaling dialog (ie. licensing only cares about total # of potential
users). Of course, this is moving target because the "activity" level
for each web user may vary greatly. This can be clarified with
hit-per-second metric feature on R3000/ER platform, but not available
today.
- 8e6 hit-per-second performance metrics are
attached below. Unfortunately, no tool is readily available to
easily determine hit-per-second for traffic being parsed by 8e6 R3000
filter (ie. existing customer and want to verify appropriate R3000
model).
-
|
Document Saved Successfully
|
|
|
|
|
|
|
