System Tuning in /etc/system:
set ip:ip_soft_rings_cnt = 16
Network Tuning:
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_xmit_hiwat 131072
ndd -set /dev/tcp tcp_recv_hiwat 131072
ndd -set /dev/tcp tcp_naglim_def 1
Network configuration:
1x XAUI 10Gbit NIC, 1x onboard 1Gbit NIC
Disk and File system configuration:
2x 146GB SAS disks for OS and application software using UFS.
2x 32GB SSD disks for logs and JMS persistence filestore using ZFS.
Configuration notes:
Four application server instances were hosted in 4 separate Solaris Containers.
Three Containers were bound to separate processor sets where each pset
consisted of 4 cores (32 HW threads) using resource pools.
The fourth container used the default processor set.
The Solaris Container and Resouce Pool configuration is in the FDA.
Interrupts were enabled on one HW strand per core.
Each Container on the system was connected to 2 subnets.
The first subnet in each container was used for driver access and
connected to the 10 GbE switch.
All 4 containers shared one 10Gbit NIC for this subnet
The second subnet in each container was used for database access
where all 4 containers shared a 1GBit NIC for this subnet.

Tablespace sizes were increased to support the Injection rate.
Scripts to create the DB are included in the FDA.
Table and index initrans were modified.
The following tables were horizontally partitioned:
C_customerinventory, C_customer, M_workorder, M_inventory,
O_orders, O_orderline, S_component, and S_purchase_orderline.
The M_parts and M_bom tables were hash clustered.
Automatic segment space management was used for all tablespaces.
System managed undo was used.
Table locks were disabled during the run using disable_locks.sh script.

To ensure database durability, RAID 1 (mirror disks)
was used for the database files and logs maintained
on the StorageTek ST2540 & 2501 Storage Arrays.
Each application server used a pair of internal SSD disks
using a ZFS mirror to provide durability for the
server logs and JMS persistence filestore.

Storage Requirement Info:

A 75 minute run at an injection rate of 5700 increased storage by 6310 MB
This extrapolates to 121 GB storage for a 24 hour run.
The database was configured with 17TB of storage.
Four sets of Sun StorageTek 2540/2501 daisy-chained pairs were configured
as 8 RAID 1 logical drives for the database files.
Two Sun StorageTek 2540 FC Arrays (12 x 146GB) where configured
as 2 RAID 1 logical drives to store the database redo logs.