HP Integrity NonStop J-Series - Manual (Page 187)

Web ViewPoint User Guide Version 5.14 - 528226-014 187
6.3 PERFORMANCE CONSIDERATIONS
6.3.1 NONSTOP SERVER CONSIDERATIONS
For Events Live if the option is to ‘Start With last n messages’ the performance depends on how many residents
the distributor (FDIST) has to travel to fetch the EMS messages.
In case of last n messages, it visits each resident one-by-one, fetches the last n messages of each and displays them
after going through all the residents. Thereafter it displays the live messages as they arrive at the collector of any
resident.
So the greater the number of residents, the more time it will take to display EMS messages.
Note: This is only in case of ‘Start with Last messages’ and not in case of ‘Start With Last minutes’.
In Events Query and Token Analyzer also the user might face the same performance issue.
When filtering options are used for Events (Live/ Query/ Token Analyzer) while trying to fetch EMS messages,
the distributor (FDIST) searches for the last EMS messages matching the filtering criteria for each of the
resident selected. This might take time. It depends on
 How far FDIST needs to search to fetch events satisfying the filter criteria.
 How many residents it needs to search one–by-one.
Complex filtering, in particular text search, may increase Web ViewPoint processing overhead. Complex filtering
should be done with care if performance is an issue.
[Back to TOC]
6.3.2 WINDOWS CLIENT
Please refer to Section 6.2 for recommended PC configurations.
Benchmark testing was done on Internet Explorer with different PC configurations to see the behavior of Web
ViewPoint – Events – Live feature. Different MAXEVENTS settings were used (the MAXEVENTS param determines
the number of events that a Live screen will show before “reloading”). Below are the tabulated findings:
Benchmark at 500
PC Configuration Event Burst Rate System Affects / Memory Usage
Single core, 2.1 GHz,
1 GB
Up to 10 Events per second
• No lag
• CPU Usage ranges from 70 to 80%
Dual core, 2.1 GHz, 1
GB
Up to 10 Events per second
• No lag
• CPU Usage ranges from 35 to 40%