Dear K.Guy krub,
Sorry for my late response. Please kindly find the sizing calculation for HP RUM as below information and the attached for RUM probe calculation sizing as for your reference krub.
The RUM solution has comprised of 3 components which each of them is affected by parameter as listed below:
Component Sizing Factor
RUM Probe Volume of traffic in Mbps (Mbits/sec)
RUM Engine Volume of hits in pages/sec
RUM Repository Amount of data:
- session click stream enable/disable
- snapshots on error enable/disable
• HP has rule of thumb that we can use as following: 20Mbps ~ 100 Pages/sec ~ 50 samples/sec
RUM Probe Sizing:
RUM probe v9.10 can handle traffic up to ~250 Mbps, depend on the below factor. If the traffic generated is more than this limit, the probe will crash and restart every few minutes.
- Total amount of HTTP traffic: depending on the total traffic being generated by the application, if the traffic is greater than 250 Mbps, then we will need additional probe and split the number of client users between probe to distribute the load.
- Total amount of HTTPS traffic: if HTTPS traffic is being generated which needs to be monitored; there will be about 10% reduction in maximum Mpbs
- Snapshot On Event Definitions: full snapshot mode can add up to ~202Mpbs
- Event Text Pattern: A minimum of 10 text pattern event can add up to ~70 Mpbs
RUM Engine Sizing:
If the number of pages being handled by the Engine is more than 500 Pages/sec, then we should have an additional engine. Also, this depends on the number of samples/sec a BSM instance can handle.
Additionally, enabling Session clickstreams which stores the pages and snapshots included in a user session can influence the capacity of the engine as given below:
Clickstream Enabled Pages / Sec Snapshots on Error
No 800 0
Yes 500 0
Yes 450 1 Page back
Yes 300 >= 2 Pages back
RUM Repository:
With clickstream and snapshot on error enable, RUM repository will store the majority of the data and requires about 400 GB per 2 weeks of traffic
Dear K.Guy krub,Sorry for my late response. Please kindly find the sizing calculation for HP RUM as below information and the attached for RUM probe calculation sizing as for your reference krub.The RUM solution has comprised of 3 components which each of them is affected by parameter as listed below:Component Sizing FactorRUM Probe Volume of traffic in Mbps (Mbits/sec)RUM Engine Volume of hits in pages/secRUM Repository Amount of data:- session click stream enable/disable- snapshots on error enable/disable• HP has rule of thumb that we can use as following: 20Mbps ~ 100 Pages/sec ~ 50 samples/secRUM Probe Sizing:RUM probe v9.10 can handle traffic up to ~250 Mbps, depend on the below factor. If the traffic generated is more than this limit, the probe will crash and restart every few minutes. - Total amount of HTTP traffic: depending on the total traffic being generated by the application, if the traffic is greater than 250 Mbps, then we will need additional probe and split the number of client users between probe to distribute the load.- Total amount of HTTPS traffic: if HTTPS traffic is being generated which needs to be monitored; there will be about 10% reduction in maximum Mpbs- Snapshot On Event Definitions: full snapshot mode can add up to ~202Mpbs- Event Text Pattern: A minimum of 10 text pattern event can add up to ~70 MpbsRUM Engine Sizing:If the number of pages being handled by the Engine is more than 500 Pages/sec, then we should have an additional engine. Also, this depends on the number of samples/sec a BSM instance can handle.Additionally, enabling Session clickstreams which stores the pages and snapshots included in a user session can influence the capacity of the engine as given below:Clickstream Enabled Pages / Sec Snapshots on ErrorNo 800 0Yes 500 0Yes 450 1 Page backYes 300 >= 2 Pages backRUM Repository:With clickstream and snapshot on error enable, RUM repository will store the majority of the data and requires about 400 GB per 2 weeks of traffic
การแปล กรุณารอสักครู่..