Itron Enterprise Edition Meter Data Management Benchmark On HP Servers

Itron Enterprise Edition Meter Data Management benchmark
on HP servers
IEE version 5.2 Release 13
Executive summary............................................................................................................................... 3
Test environment .................................................................................................................................. 4
Application server ............................................................................................................................ 4
Database server............................................................................................................................... 4
Driver components ........................................................................................................................... 5
Test data generators......................................................................................................................... 5
Other tools ...................................................................................................................................... 5
Network setup ................................................................................................................................. 5
Setup diagram................................................................................................................................. 6
Test methodology................................................................................................................................. 6
Meter configuration for benchmark testing .......................................................................................... 6
Workflow........................................................................................................................................ 7
Benchmark scenario ......................................................................................................................... 8
Horizontal scale-out testing................................................................................................................ 9
MDM system stair step optimization .............................................................................................. 11
Testing regimen ............................................................................................................................. 12
Risks............................................................................................................................................. 13
Schedule....................................................................................................................................... 13
Import process ............................................................................................................................... 13
Aggregate and export .................................................................................................................... 14
Test results ........................................................................................................................................ 14
1 Million Meter IMPORT ................................................................................................................. 14
(1/20th of) 1 Million Meter EXPORT ................................................................................................ 14
5 Million Meter IMPORT ................................................................................................................. 15
(1/20th of) 5 Million Meter EXPORT ................................................................................................ 15
Database server performance.......................................................................................................... 16
1 Million Meter IMPORT.............................................................................................................. 16
1 Million Meter EXPORT.............................................................................................................. 18
5 Million Meter IMPORT.............................................................................................................. 20
5 Million Meter EXPORT.............................................................................................................. 22
4-way application server performance.............................................................................................. 24
8-way application server performance.............................................................................................. 26
Database server parameters................................................................................................................ 28
Kernel parameters.......................................................................................................................... 28
File system parameters.................................................................................................................... 28
File system mount options ............................................................................................................ 28
File system layout ....................................................................................................................... 29
VxFS file system tuning parameters ............................................................................................... 29
For more information.......................................................................................................................... 33

Executive summary
As the Energy and Water industries continue to automate meter data collection, and build out one-
way and two-way networks to the home, robust meter data management (MDM) has become a
critical necessity. Itrons vast experience in this field is embodied in its MDM product line, Itron
Enterprise Edition (IEE). IEE was first released commercially in early 2004. Since then, six utility
customers have implemented IEE meter data management and 14 more are in the process of
implementing the solution. The current version is v5.3.
This benchmark effort is intended to provide MDM buyers with a clear picture of IEEs scalability, as
well as Itrons and HPs commitment to the technologies required for very large scale AMI (advanced
metering infrastructure) initiatives.
We are proud to report that IEE and HP platforms accomplished these goals, and buyers can be more
confident due to these results.
1. The benchmark has shown we can scale from metro-area size AMI networks of 1 million hourly
meters, to regional size networks of over 5 million hourly meters.
2. We validated that the tested architecture enables an incremental build out of computing resources
as the AMI network deploys to maximize return on investment (ROI).
3. We validated that the tested architecture can import, validate and generate time-of-use (TOU)
billing exports for 5 million hourly meters within aggressive processing windows. Included is time
for restarts on a system failure.
4. We demonstrated scalability using the very latest general purpose computing hardware and
infrastructure. No exotic configurations or hardware/software computing infrastructure is required.
5. Itrons 25 years experience with the "day-in-the-life" processing of the meter-to-cash workflow was
leveraged to create a valid, realistic set of testing scenarios in the new world of large scale AMR
(automatic meter reading) and AMI.
Itron partnered with Hewlett Packard Company (HP), to provide independent validation and
verification of Itrons claims.
This report contains the results of those tests. The results show that Itrons flagship enterprise software
solution does, in fact, meet and exceed the required performance and scalability demands and could
flexibly scale to meet the growing future needs of its customers.
Specifically, Itrons architecture is designed to scale both horizontally and vertically. Vertical scaling
allows a company to expand its suite of hardware by either expanding existing hardware or
purchase new platforms. More processors, more memory, and more disk arrays typically are a part of
a vertical scaling approach. On the other hand, Itrons horizontal scale out strategy ensures
companies can increase raw processing performance simply by adding more application servers to
an existing Itron system. The emphasis in horizontal scale out is to be able to use relatively low cost,
commodity type computers that are added to an existing network and immediately begin participating
in the asynchronous processing of the myriad tasks required to process information.
Itron spent six months in its internal performance labs in Spokane and Raleigh tweaking and
optimizing hardware and software components. Then, during the months of June, July, and August
2006 Itron employees teamed up with HP employees in HPs Marlborough, Massachusetts lab. Itron
installed its enterprise MDM application called Itron Enterprise Edition (IEE) and over a period of time
ran large-scale scenarios while monitoring an array of hardware and software components. The goal
was to make sure the performance of Itrons MDM solution not only meets todays needs of a large
utility company, but will be able to grow as Itrons customers deploy increasingly sophisticated
metering solutions.
3
The results of the performance tests and benchmarks are contained in the report below. In all cases
HP and Itron were able to verify Itrons MDM solution does, in fact, meets and usually actually
exceeds all the performance requirements necessary to satisfy very large scale installations upwards
of five (5) million residential AMI hourly interval meters.
Test environment
Application server
7 HP ProLiant DL585 servers running Microsoft Windows Server 2003:

2 with (4) 2.4 GHz Single-Core AMD Opteron 850 CPUs, 1MB L2 cache, 16 GB RAM,
(4) 146 GB hard drives

(4) 72 GB hard drives.

(4) 72 GB hard drives.

1 with (4) 2.2 GHz Dual-Core AMD Opteron 875 CPUs, 1MB L2 cache, 32 GB RAM,
(4) 146 GB hard drives

Database server
Hardware Platform HP Integrity rx8620 server
Operating System HP-UX 11i v2 (AR0604)
Machine Architecture Intel Itanium 2 HP rx8620 server
Number of CPUs 32 (using HP mx2 CPU modules)
1.1 GHz Itanium 2 with 4MB L3 cache
Memory size (GB) 128
Disk Space (GB) SAN1 HP StorageWorks 5000 Enterprise Virtual Array (EVA5000) 6TB
Dual HSV210 Active/Active SAN controllers
5737.41GB RAID 0 Striping 4 LUNs striped in software (VxVM
Symantec Veritas Volume Manager) to allow > 2TB file system. Each LUN
composing the file system was also striped in hardware by the EVA.
SAN2 HP StorageWorks EVA5000 10TB
Dual HSV210 Active/Active SAN controllers
9562GB RAID 1+0 or 10 Striped Mirror
The SANs do automatic hardware RAID 0.
8 146GB SCSI drives in the Integrity server. Oracle was installed on the
local SCSI drives.
Number of IO Devices 198
Additional Information There are 4 dual port Fibre Channel HBAs in the Integrity server. One port of
each adapter goes to each SAN (two SANs).
4
The HBAs were 2 Gb adapters.
Each LUN in the SANs had 16 paths to it. Dynamic multi-pathing was
configured using the DMP feature of the Veritas Volume Manager.
Software Oracle10g Release 1 (10.1) Enterprise Edition
Oracle10g Release 1 Patch Set 10.1.0.4
Oracle Critical Patch Update January 2006,
CPUJan2006 (Interim Patch 4751928)
Network There were two Gigabit network interfaces used in each box.

Driver components
Oracle .NET Provider
Test data generators
Itrons proprietary Configuration Data Generator (Data Squid)
Itrons proprietary Reading Generator
Other tools
SAR
Toad (diagnostic SQL tool)
Oracle Enterprise Manager
Network setup
Two network interfaces cards (NIC) per application and database server.
The first NIC was on a "public" network to enable remote access and
monitoring.
The second NIC was for a dedicated connection to the database server and
the other application servers. This was a "private network segment.
Traffic on the private net was isolated in a VLAN set up in the HP ProCurve
switch. This switch controlled the entire network in HPs lab.
The network was a gigabit switched Ethernet.
5
Setup diagram

Figure 1. Setup diagram

Test methodology
Meter configuration for benchmark testing
Itrons test plan included running tests using databases with meter configurations of one (1) and five
(5) million meters. We created a hierarchical configuration model with multiple parallel relationships
to ensure our test used a configuration of sufficient complexity to correctly model how our largest
customers intend to use the IEE MDM solution.
Our mission for the benchmark testing was to establish that the IEE MDM solution has the ability to
support large numbers of meter configurations and to benchmark the performance of the application
during data loads and exports. Moreover, we hoped to be able to learn how to better estimate
hardware sizing for future sales proposals and customer installations.
The test configuration consisted of one customer, one account, service-point, and meter with one
hourly interval channel and one register channel. For the one interval channel the TOU definition
required six (6) TOU billing channels per season which provided export buckets for On/Off peak
usage, demand, and peak time. These were used for the export tests.
6
The TOU schedule used during our testing reflects a multi-season, two-period definition (on-peak, off-
peak). On-peak usage was defined for both Summer and Winter schedules, and had one Holiday
schedule assigned. This schedule resulted in 12 new TOU channels but since we loaded data into a
single season we only created six channels for the Summer season.
Workflow
Itrons objective was to model a day in the life of a utility. Figures 2a and 2b, below, depict what
Itron considers a typical daily processing scenario.
Figure 2a shows business entity relationships and Figure 2b depicts a typical utility business process.

Figure 2a. Typical Utility Business Entity Relationships

7

Figure 2b. Typical Business Process in a Utility Company

Benchmark scenario
Itrons objective was to benchmark and measure the time required to process very large sets of data
that are essential to the core revenue process in a utility company. The data format for the import files
was the ASCII text format defined for Itrons file import adapters. There was no particular significance
attached to the decision to use the ASCII format other than its simplicity when generating test data
files. Each data file contained exactly 24 hourly interval data and the register stop read.
Load and export tests were repeated for the one and five million meter configurations. HP made
available a 15 Terabyte SAN array. Unfortunately, Itron discovered this only allowed us to upload
three months worth of historical data before running out of room. An important lesson learned was
that ultra large-scale installations will be highly storage intensive. This potentially will affect which IT
skill-sets need to be available to manage such a configuration.
Another important lesson is that the network itself can become a significant bottleneck if not correctly
designed. The minimum speed for a network should be a gigabit switched environment.
The export tests verified the time to export a typical cycle, or 1/20 of the meters per day for billing.
These tests were also conducted with the system described above and while creating several cycles
each with an Aggregation and Export assigned. Itron has spent significant time optimizing the IEE
lookup and caching algorithms to ensure lookup information is only retrieved once and then re-used
during multiple processes. The two exports we ran exported the TOU buckets assigned to each service
point.
The export adapters were scheduled in mass by another adapter called the export scheduler. This
adapter read task definitions from a configuration file and then created export tasks in the IEE Task
Management System (TMS). This approach allowed the systems built-in load balancing to handle
distributing the tasks among all available task runners.
8
Examples of export tests were creating MV90 Mainframe, Lodestar, ReadingXML, or the MV90
spreadsheet format files. These file formats are germane to many core business processes in Itrons
customer base.
A realistic AMI process test case must incorporate reading data validation and data storage. IEEs
highly optimized data importing sub-system accomplishes each of these tasks for each meter, each
day. Further details about the process can be provided by Itron upon request.

Figure 3. Detailed Readings Import Data Flow Diagram Validation Sub-System

Horizontal scale-out testing
Itrons horizontal application scale-out strategy strives to obtain high levels of concurrency in the large
batch oriented processing steps in MDM. Itrons Task Management Systems (TMS) is a simple, but
9
flexible work dispatcher that splits these large processing steps into hundreds of tasks that can be
processed concurrently. The TMS is universally available inside the Itron system and assigns available
work to available Task Runners. A Task Runner is an Itron software component (program) that is
designed to independently poll the TMS and request any work if it is available. Task Runners can be
distributed across several computers, and each computer can host several Task Runners.
Thus, you can add more application servers to run more tasks, but you can also run more Task
Runners on each application server. Itron did both during these tests. We used up to six application
servers each running up to nine Task Runners. We modified combinations of these to ensure we could
measure the scaling impact as we added more servers and/or runners.
By easily manipulating these run-time configuration options, Itron was able to validate the scale-out
architecture of the TMS. From the throughput numbers in Figures 4 and 5 one can see a nearly 80%
linear scalability of the solution. Obtaining throughput of up to 24,000 interval readings imported
and validated per second! More than twice as much as the 12,000 intervals/second required for a 5
million hourly interval meter network with a 4 hour import window.
The HP laboratory was critical for Itron to firm up hardware and task runner configurations needed to
address various customer scenarios and roll-out strategies.

Figure 4. Horizontal Scale-Out using Task Runners

10

Figure 5. Horizontal Scale-Out using Application Servers

MDM system stair step optimization
Another important design consideration in a high performance MDM system is that as more
application servers and Task Runners are added, at some point you will overwhelm the databases
ability to keep up with the incoming data. That is, the combination of application servers and Task
Runners will saturate the database server (or cluster) and thus performance will drop off because the
database environment no longer runs at peak efficiency. Contention, collisions, and other issues will
now degrade overall performance.
For example, youll note in Figures 4 and 5 that at a certain point performance began to level off and
actually decreased. This was because the database server was running at maximum capacity and
when its saturation levels were reached it could no longer efficiently and concurrently process the
incoming data. At that point, overall performance for the entire process slowly began to degrade.
Therefore, every scale-out strategy needs to include the recognition that this is a stair-step, incremental
process. There is a sweet spot for how many Task Runners can concurrently run on an application
server, but more importantly there also is a sweet spot for the entire system that is the ideal
combination of database servers (or cluster), application servers, and Task Runners.
In other words, when you have a certain capacity inherent in your database server you will be able to
add more application servers and Task Runners up to the point you max out the database.
You then have to scale up the database environment before additional performance gains can be
achieved by adding more application servers and/or Task Runners. This is illustrated in Figure 6.
11

Figure 6. Stair-Step Optimization of Entire MDM Environment

Testing regimen
The tests below were run numerous times under a variety of conditions to ensure we could capture
performance data and correctly measure it against baseline information.
Measure the load rate using the ASCII adapter with validation. Two rules were used; the High/Low
limit and the usage tolerance check.
Measure the aggregation and export rates for 1/20th of the service points.
Vary the number of application servers from one to six for one (1) million and five (5) million meters
to measure horizontal scaling. The HP application servers used were 4-way machines.
12
Risks
Database tuning If Oracle was not well tuned for the hardware it was running on, the results
could be questionable.
Lack of available remote access to the lab. This was not a problem during our testing.
Possible issues with bulk loading the configuration and historical reading data. We had a few
glitches but overall the loading process worked well.
Schedule
The following were the time estimates for getting the system up and running. We knew that after the
system was loaded some time would be needed between runs to tune the database. Once we were
satisfied with the tuning we then reran our testing regimen.
Generating the Configuration data runs at the rate of 10,000/hour

1 million meters 1.7 hours

Loading the Configuration data ~ rate of 1.5 million/hour


Generating Historical readings for 11 months runs at a rate about 72 minutes/million-meters/month.

5 million meters 665 hours

Loading Historical data; count on 30 minutes per 1 Million configurations per month of readings
(assuming 60 minute intervals)

1 million meters (11 months) 0.5 hours
5 million meters (11 months) 2.5 hours

Generate Cycle import for measuring aggregation/export speed on cycle (1/20th of one and five
million exports)

Loading Cycles 1 hour
Run the Matrix 2 weeks

Import process
We imported readings for one and five million meters and performed validation.
26 readings per channel per day.
13
24 were hourly intervals.
2 were register reads.
The readings were delivered in one 24 hour chunk.
We varied the number of files, meters per file and multiple files with each file containing 24 hours
of data for 1,000, 5,000 and 10,000 meters.
From this established the optimum number of meters per file was 1,000.
Aggregate and export
We ran an Aggregation and Export for 1/20th of all meters to simulate a cycle.
Tests were performed for one million and five million meters.
We aggregated the data into six TOU buckets for a month for each meter.
We exported the data using the ReadingXML format
We exported six TOU channels and total usage for each meter.
Test results
1 Million Meter IMPORT: 23,168.16 intervals per second

Entire Process
Submitted_Date 2006-08-29
TextTypeId TextReadingImport
Process_Minutes 13
Files_Processed 1,000

Per Runner
Min_Process_minutes 0.47
Max_Process_Minutes 1.97
Avg_process_minutes 1.01
Intervals_Second_per_Runner 429.04

(1/20th of) 1 Million Meter EXPORT: 11.41 exported bills per second

Entire Process
TextTypeId ReadingXmlExport
Process_Minutes 109.52

Per Runner
14

5 Million Meter IMPORT: 21,081.08 intervals per second

Entire Process
TextTypeId TextReadingImport
Files_Processed 5000

Per Runner
Intervals_Second_per_Runner 390.39039039039

(1/20th of) 5 Million Meter EXPORT: 8.21 exported bills per second

Entire Process
TextTypeId ReadingXmlExport

Per Runner

15
Database server performance

1 Million Meter IMPORT

Database Server CPU Usage
0
20
40
60
80
100
120
11:30:59 11:33:59 11:36:59 11:39:59 11:42:59 11:45:59 11:48:59 11:51:59
%usr
%sys
%wio
%idle

Database Server Average Disk Usage
1
.
1
5
1
.
6
3
1
.
4
3
0
.
0
8
0
.
0
2
0
.
0
1
0
.
0
6
0
.
0
1
4
.
2
6
7
.
4
9
5
.
8
2
5
.
9
4
1
4
.
8
3
1
3
.
1
7
1
6
.
5
0
2
4
6
8
10
12
14
16
18

c
0
t
6
d
0

c
2
t
6
d
0

c
8
t
6
d
0
c
1
2
t
6
d
0
c
8
2
t
0
d
2
c
8
2
t
0
d
4
c
8
6
t
0
d
1
c
8
6
t
0
d
3
c
7
4
t
0
d
2
c
7
4
t
0
d
4
c
7
4
t
0
d
7
c
7
8
t
0
d
1
c
7
8
t
0
d
3
c
7
8
t
0
d
5
c
7
8
t
0
d
6
%busy

16
Oracle Enterprise Manager Metrics for 1 Million Meter IMPORT

17
Database Server Performance
1 Million Meter EXPORT

0
20
40
60
80
100
120
1
3
:
2
1
:
4
9
1
3
:
3
1
:
4
9
1
3
:
4
1
:
4
9
1
3
:
5
1
:
4
9
1
4
:
0
1
:
4
9
1
4
:
1
1
:
4
9
1
4
:
2
1
:
4
9
1
4
:
3
1
:
4
9
1
4
:
4
1
:
4
9
1
4
:
5
1
:
4
9
1
5
:
0
1
:
4
9
1
5
:
1
1
:
4
9
1
5
:
2
1
:
4
9
1
5
:
3
1
:
4
9
%usr
%sys
%wio
%idle

0
10
20
30
40
50
60
70

c
0
t
6
d
0

c
2
t
6
d
0

c
8
t
6
d
0

c
1
2
t
6
d
0

c
8
2
t
0
d
2

c
8
2
t
0
d
4

c
8
6
t
0
d
1

c
8
6
t
0
d
3

c
7
4
t
0
d
2

c
7
4
t
0
d
4

c
7
4
t
0
d
7

c
7
8
t
0
d
1

c
7
8
t
0
d
3

c
7
8
t
0
d
5

c
7
8
t
0
d
6

%busy

18
Oracle Enterprise Manager Metrics for 1 Million Meter EXPORT

19
5 Million Meter IMPORT

Database CPU Usage
0
20
40
60
80
100
120
1
6
:
3
2
:
4
5
1
6
:
3
7
:
4
5
1
6
:
4
2
:
4
5
1
6
:
4
7
:
4
5
1
6
:
5
2
:
4
5
1
6
:
5
7
:
4
5
1
7
:
0
2
:
4
5
1
7
:
0
7
:
4
5
1
7
:
1
2
:
4
5
1
7
:
1
7
:
4
5
1
7
:
2
2
:
4
5
1
7
:
2
7
:
4
5
1
7
:
3
2
:
4
5
1
7
:
3
7
:
4
5
1
7
:
4
2
:
4
5
1
7
:
4
7
:
4
5
1
7
:
5
2
:
4
5
1
7
:
5
7
:
4
5
%usr
%sys
%wio
%idle

0
10
20
30
40
50
60
70

c
0
t
6
d
0

c
2
t
6
d
0

c
8
t
6
d
0
c
1
2
t
6
d
0
c
7
4
t
0
d
2
c
7
4
t
0
d
4
c
7
4
t
0
d
7
c
7
8
t
0
d
1
c
7
8
t
0
d
3
c
7
8
t
0
d
5
c
7
8
t
0
d
6
c
8
2
t
0
d
2
c
8
2
t
0
d
4
c
8
6
t
0
d
1
c
8
6
t
0
d
3
%busy

20
Oracle Enterprise Manager Metrics for 5 Million Meter IMPORT

21
5 Million Meter EXPORT

0
20
40
60
80
100
120
1
8
:
3
4
:
0
4
1
9
:
0
9
:
0
4
1
9
:
4
4
:
0
4
2
0
:
1
9
:
0
4
2
0
:
5
4
:
0
4
2
1
:
2
9
:
0
4
2
2
:
0
4
:
0
4
2
2
:
3
9
:
0
4
2
3
:
1
4
:
0
4
2
3
:
4
9
:
0
4
0
:
2
4
:
0
4
0
:
5
9
:
0
4
1
:
3
4
:
0
4
2
:
0
9
:
0
4
2
:
4
4
:
0
4
3
:
1
9
:
0
4
3
:
5
4
:
0
4
4
:
2
9
:
0
4
5
:
0
4
:
0
4
%usr
%sys
%wio
%idle

0
10
20
30
40
50
60
70

c
0
t
6
d
0

c
2
t
6
d
0

c
8
t
6
d
0
c
1
2
t
6
d
0
c
8
2
t
0
d
2
c
8
2
t
0
d
4
c
8
6
t
0
d
1
c
7
4
t
0
d
2
c
7
4
t
0
d
4
c
7
4
t
0
d
7
c
7
8
t
0
d
1
c
7
8
t
0
d
3
c
7
8
t
0
d
5
c
7
8
t
0
d
6
c
8
6
t
0
d
3
%busy

22
Oracle Enterprise Manager Metrics for 5 Million Meter EXPORT

23
4-way application server performance
1 Million Meter Import 4 Way
0
5
10
15
20
25
2
5
:
2
3
.
4
2
6
:
0
8
.
4
2
6
:
5
3
.
4
2
7
:
3
8
.
4
2
8
:
2
3
.
4
2
9
:
0
8
.
4
2
9
:
5
3
.
4
3
0
:
3
8
.
4
3
1
:
2
3
.
4
3
2
:
0
8
.
4
3
2
:
5
3
.
4
3
3
:
3
8
.
4
3
4
:
2
3
.
4
3
5
:
0
8
.
4
3
5
:
5
3
.
4
3
6
:
3
8
.
4
3
7
:
2
3
.
4
3
8
:
0
8
.
5
3
8
:
5
3
.
5
3
9
:
3
8
.
5
4
0
:
2
3
.
5
4
1
:
0
8
.
5
Ti me
%
C
P
U
% Processor Time

0
5
10
15
20
25
5
0
:
1
5
.
6
5
5
:
1
5
.
6
0
0
:
1
5
.
6
0
5
:
1
5
.
6
1
0
:
1
5
.
6
1
5
:
1
5
.
6
2
0
:
1
5
.
6
2
5
:
1
5
.
6
3
0
:
1
5
.
6
3
5
:
1
5
.
6
4
0
:
1
5
.
6
4
5
:
1
5
.
6
5
0
:
1
5
.
6
5
5
:
1
5
.
6
0
0
:
1
5
.
6
0
5
:
1
5
.
6
1
0
:
1
5
.
6
1
5
:
1
5
.
6
2
0
:
1
5
.
6
2
5
:
1
5
.
6
3
0
:
1
5
.
6
3
5
:
1
5
.
6
4
0
:
1
5
.
6
4
5
:
1
5
.
6
5
0
:
1
5
.
6
%CPU
T
i
m
e
% Processor Time

24
1 Million Meter Export 4 Way
0
10
20
30
40
50
60
70
80
90
1
6
:
1
8
.
4
2
1
:
3
3
.
4
2
6
:
4
8
.
5
3
2
:
0
3
.
5
3
7
:
1
8
.
5
4
2
:
3
3
.
6
4
7
:
4
8
.
6
5
3
:
0
3
.
6
5
8
:
1
8
.
6
0
3
:
3
3
.
6
0
8
:
4
8
.
6
1
4
:
0
3
.
6
1
9
:
1
8
.
6
2
4
:
3
3
.
6
2
9
:
4
8
.
6
3
5
:
0
3
.
6
4
0
:
1
8
.
6
4
5
:
3
3
.
6
5
0
:
4
8
.
6
5
6
:
0
3
.
6
0
1
:
1
8
.
6
0
6
:
3
3
.
6
1
1
:
4
8
.
6
Ti me
%
C
P
U
% Processor Time - 4 Way

5 Million Meter Aggregation/Export 4 Way
0
20
40
60
80
100
120
3
1
:
2
2
.
4
5
2
:
3
7
.
4
1
3
:
5
2
.
4
3
5
:
0
7
.
4
5
6
:
2
2
.
4
1
7
:
3
7
.
4
3
8
:
5
2
.
4
0
0
:
0
7
.
4
2
1
:
2
2
.
4
4
2
:
3
7
.
4
0
3
:
5
2
.
4
2
5
:
0
7
.
4
4
6
:
2
2
.
4
0
7
:
3
7
.
4
2
8
:
5
2
.
4
5
0
:
0
7
.
4
1
1
:
2
2
.
4
3
2
:
3
7
.
4
5
3
:
5
2
.
4
1
5
:
0
7
.
4
3
6
:
2
2
.
4
5
7
:
3
7
.
4
1
8
:
5
2
.
4
4
0
:
0
7
.
4
Ti me
%
C
P
U
% Processor Time SPA67

25
8-way application server performance
0
2
4
6
8
10
12
2
6
:
0
5
.
9
2
6
:
5
0
.
9
2
7
:
3
5
.
9
2
8
:
2
0
.
9
2
9
:
0
5
.
9
2
9
:
5
0
.
9
3
0
:
3
5
.
9
3
1
:
2
0
.
9
3
2
:
0
5
.
9
3
2
:
5
0
.
9
3
3
:
3
5
.
9
3
4
:
2
0
.
9
3
5
:
0
5
.
9
3
5
:
5
0
.
9
3
6
:
3
5
.
9
3
7
:
2
0
.
9
3
8
:
0
5
.
9
3
8
:
5
0
.
9
3
9
:
3
5
.
9
4
0
:
2
0
.
9
4
1
:
0
5
.
9
4
1
:
5
0
.
9
Ti me
%
C
P
U
% Processor Time

0
2
4
6
8
10
12
5
3
:
1
1
.
6
5
7
:
5
6
.
6
0
2
:
4
1
.
6
0
7
:
2
6
.
6
1
2
:
1
1
.
6
1
6
:
5
6
.
6
2
1
:
4
1
.
6
2
6
:
2
6
.
6
3
1
:
1
1
.
6
3
5
:
5
6
.
6
4
0
:
4
1
.
6
4
5
:
2
6
.
6
5
0
:
1
1
.
6
5
4
:
5
6
.
6
5
9
:
4
1
.
6
0
4
:
2
6
.
6
0
9
:
1
1
.
6
1
3
:
5
6
.
6
1
8
:
4
1
.
6
2
3
:
2
6
.
6
2
8
:
1
1
.
6
3
2
:
5
6
.
6
3
7
:
4
1
.
6
4
2
:
2
6
.
6
4
7
:
1
1
.
6
5
1
:
5
6
.
6
Ti me
%
C
P
U
% Processor Time

26
1 Million Meter Export 8 Way
0
10
20
30
40
50
60
70
1
6
:
2
4
.
5
2
1
:
0
9
.
5
2
5
:
5
4
.
5
3
0
:
3
9
.
5
3
5
:
2
4
.
5
4
0
:
0
9
.
5
4
4
:
5
4
.
5
4
9
:
3
9
.
5
5
4
:
2
4
.
5
5
9
:
0
9
.
5
0
3
:
5
4
.
5
0
8
:
3
9
.
5
1
3
:
2
4
.
5
1
8
:
0
9
.
5
2
2
:
5
4
.
5
2
7
:
3
9
.
5
3
2
:
2
4
.
5
3
7
:
0
9
.
5
4
1
:
5
4
.
5
4
6
:
3
9
.
5
5
1
:
2
4
.
5
5
6
:
0
9
.
5
0
0
:
5
4
.
5
0
5
:
3
9
.
5
1
0
:
2
4
.
5
1
5
:
0
9
.
5
Ti me
%
C
P
U
% Processor Time

5 Million Meter Aggregation/Export 8 Way
0
10
20
30
40
50
60
70
80
3
1
:
2
1
.
6
5
2
:
3
6
.
6
1
3
:
5
1
.
6
3
5
:
0
6
.
6
5
6
:
2
1
.
7
1
7
:
3
6
.
8
3
8
:
5
1
.
8
0
0
:
0
6
.
9
2
1
:
2
1
.
9
4
2
:
3
6
.
9
0
3
:
5
1
.
9
2
5
:
0
6
.
9
4
6
:
2
1
.
8
0
7
:
3
6
.
8
2
8
:
5
1
.
8
5
0
:
0
6
.
8
1
1
:
2
1
.
8
3
2
:
3
6
.
7
5
3
:
5
1
.
7
1
5
:
0
6
.
7
3
6
:
2
1
.
7
5
7
:
3
6
.
6
1
8
:
5
1
.
6
4
0
:
0
6
.
6
%CPU
T
i
m
e
% Processor Time SPA104

27
Database server parameters
Kernel parameters
The following parameters were changed from their default values
Tunabl e Val ue Expr essi on
dbc_max_pct 20 20
ksi _al l oc_max 65536 npr oc*8
max_async_por t s 1024 1024
max_t hr ead_pr oc 1024 1024
maxf i l es 8192 8192
maxf i l es_l i m 16384 16384
maxssi z 134217728 134217728
maxssi z_64bi t 1073741824 1073741824
maxupr c 7372 npr oc*9/ 10
msgmap 4098 2+msgmni
msgmni 4096 4096
msgseg 32767 32767
msgt ql 4096 4096
nf i l e 124928 15*npr oc+2048
ni node 67584 8*npr oc+2048
nkt hr ead 14352 npr oc*7/ 4+16
npr oc 8192 8192
npt y 200 200
nst r pt y 200 200
scsi _max_qdept h 128 128
semmni 4096 4096
semmns 8192 semmni *2
semmnu 8188 npr oc- 4
shmmax 1. 07374E+11 1. 07374E+11
Shmmni 512 512
vps_cei l i ng 64 64

File system parameters
File system mount options

# Syst em/ et c/ f st ab f i l e. St at i c i nf or mat i on about t he f i l e syst ems
# See f st ab( 4) and sam( 1M) f or f ur t her det ai l s on conf i gur i ng devi ces.
/ dev/ vx/ dsk/ r oot dg/ r oot vol / vxf s del ayl og 0 1
/ dev/ vx/ dsk/ r oot dg/ st andvol / st and vxf s t r anf l ush 0 1
/ dev/ vx/ dsk/ r oot dg/ t mpvol / t mp vxf s del ayl og 0 2
/ dev/ vx/ dsk/ r oot dg/ homevol / home vxf s del ayl og 0 2
/ dev/ vx/ dsk/ r oot dg/ opt vol / opt vxf s del ayl og 0 2
/ dev/ vx/ dsk/ r oot dg/ usr vol / usr vxf s del ayl og 0 2
/ dev/ vx/ dsk/ r oot dg/ var vol / var vxf s del ayl og 0 2
/ dev/ vx/ dsk/ or asof t / or ahome / u01/ app/ or acl e vxf s sui d 0 2
/ dev/ vx/ dsk/ or asof t / or at mp / u01/ or adat a/ t mp vxf s sui d 0 2
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 / u03/ or adat a vxf s
t mpl og, nodat ai nl og, convosync=di r ect , mi ncache=di r ect 0 3
28
/ dev/ vx/ dsk/ hi st dat a/ hi st vol / u01/ or adat a vxf s

File system layout

Fi l esyst em kbyt es used avai l %used Mount ed on
/ dev/ vx/ dsk/ r oot dg/ r oot vol
602224 414824 185960 69%/
/ dev/ vx/ dsk/ r oot dg/ st andvol
307200 69208 236176 23%/ st and
/ dev/ vx/ dsk/ r oot dg/ var vol
134729728 2869392 130831664 2%/ var
/ dev/ vx/ dsk/ r oot dg/ usr vol
6296632 2973584 3297096 47%/ usr
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 7
37730304 31768824 5914912 84%/ u09/ or adat a
75479040 58853752 16495408 78%/ u08/ or adat a
188725248 153843712 34609032 82%/ u07/ or adat a
188725248 108892624 79208936 58%/ u06/ or adat a
2097084416 876077104 1211468224 42%/ u05/ or adat a
1048541184 41013352 999656528 4%/ u04/ or adat a
1048541184 41016320 999653584 4%/ u03/ or adat a
/ dev/ vx/ dsk/ hi st dat a/ hi st vol
5662043136 2938528168 2702237544 52%/ u01/ or adat a
/ dev/ vx/ dsk/ or asof t / or at mp
104857600 42846 98263903 0%/ u01/ or adat a/ t mp
/ dev/ vx/ dsk/ or asof t / or ahome
20971520 8254799 11925459 41%/ u01/ app/ or acl e
/ dev/ vx/ dsk/ r oot dg/ t mpvol
819200 10184 803648 1%/ t mp
/ dev/ vx/ dsk/ r oot dg/ opt vol
6140752 3047792 3068864 50%/ opt
/ dev/ vx/ dsk/ r oot dg/ homevol
20480 8456 11944 41%/ home

VxFS file system tuning parameters

# Fi l esyst emi / o par amet er s f or / u01/ or adat a
/ dev/ vx/ dsk/ hi st dat a/ hi st vol r ead_pr ef _i o=1048576
/ dev/ vx/ dsk/ hi st dat a/ hi st vol r ead_nst r eam=32
/ dev/ vx/ dsk/ hi st dat a/ hi st vol r ead_uni t _i o=131072
/ dev/ vx/ dsk/ hi st dat a/ hi st vol wr i t e_pr ef _i o=1048576
/ dev/ vx/ dsk/ hi st dat a/ hi st vol wr i t e_nst r eam=32
/ dev/ vx/ dsk/ hi st dat a/ hi st vol wr i t e_uni t _i o=131072
/ dev/ vx/ dsk/ hi st dat a/ hi st vol pr ef _st r engt h=20
/ dev/ vx/ dsk/ hi st dat a/ hi st vol buf _br eakup_si ze=262144
/ dev/ vx/ dsk/ hi st dat a/ hi st vol di scover ed_di r ect _i osz=2048
/ dev/ vx/ dsk/ hi st dat a/ hi st vol max_di r ect _i osz=67066880
/ dev/ vx/ dsk/ hi st dat a/ hi st vol def aul t _i ndi r _si ze=8192
/ dev/ vx/ dsk/ hi st dat a/ hi st vol qi o_cache_enabl e=0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol wr i t e_t hr ot t l e=0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol max_di skq=352321536
/ dev/ vx/ dsk/ hi st dat a/ hi st vol i ni t i al _ext ent _si ze=10
29
/ dev/ vx/ dsk/ hi st dat a/ hi st vol max_seqi o_ext ent _si ze=2048
/ dev/ vx/ dsk/ hi st dat a/ hi st vol max_buf _dat a_si ze=8192
/ dev/ vx/ dsk/ hi st dat a/ hi st vol hsm_wr i t e_pr eal l oc=0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol r ead_ahead=1
/ dev/ vx/ dsk/ hi st dat a/ hi st vol i node_agi ng_si ze=0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol i node_agi ng_count =0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol f cl _maxal l oc=175694913536
/ dev/ vx/ dsk/ hi st dat a/ hi st vol f cl _keept i me=0
/ dev/ vx/ dsk/ hi st dat a/ hi st vol f cl _wi nt er val =3600
/ dev/ vx/ dsk/ hi st dat a/ hi st vol ol t p_l oad=0

/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 r ead_pr ef _i o=65536
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 r ead_nst r eam=32
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 r ead_uni t _i o=65536
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 wr i t e_pr ef _i o=65536
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 wr i t e_nst r eam=32
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 wr i t e_uni t _i o=65536
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 pr ef _st r engt h=10
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 buf _br eakup_si ze=262144
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 di scover ed_di r ect _i osz=2048
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 max_di r ect _i osz=2097152
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 def aul t _i ndi r _si ze=8192
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 qi o_cache_enabl e=0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 wr i t e_t hr ot t l e=0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 max_di skq=8388608
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 i ni t i al _ext ent _si ze=1
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 max_seqi o_ext ent _si ze=2048
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 max_buf _dat a_si ze=8192
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 hsm_wr i t e_pr eal l oc=0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 r ead_ahead=1
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 i node_agi ng_si ze=0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 i node_agi ng_count =0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 f cl _maxal l oc=32536543232
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 f cl _keept i me=0
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 f cl _wi nt er val =3600
/ dev/ vx/ dsk/ cur r ent dat a/ cur vol 1 ol t p_l oad=0


30


31
32



For more information
Itron IEE product information, http://www.itron.com
HP Energy & Utilities information, http://www.hp.com
HP Integrity servers, http://www.hp.com/go/integrity/
HP ProLiant servers, http://www.hp.com/go/proliant/
HP StorageWorks Enterprise Virtual Arrays, http://www.hp.com/go/eva/
To help us improve our documents, please provide feedback at www.hp.com/solutions/feedback.

2007 Hewlett-Packard Development Company, L.P. The information contained
herein is subject to change without notice. The only warranties for HP products and
services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries.
AMD Opteron are trademarks of Advanced Micro Devices, Inc. Oracle is a
registered trademark of Oracle Corporation and/or its affiliates. IEE and Itron are
registered trademarks of Itron.
4AA1-5527ENW, October 2007

Itron Enterprise Edition Meter Data Management Benchmark On HP Servers

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Itron Enterprise Edition Meter Data Management Benchmark On HP Servers

Hochgeladen von

Copyright:

Verfügbare Formate

Itron Enterprise Edition Meter Data Management benchmark

Das könnte Ihnen auch gefallen