Review of Intalio|Server Performance

 

Performance

 

Performance differs greatly depending on many different factors

• process design and complexity
• level of persistence
• transport protocols and quality of service
• latency of web services
• hardware, network, JVM and operating system

To give you an idea of the kinds of performance you can expect from Intalio|BPMS we have run some benchmark tests on standard software and hardware configuration.

Hardware and Software Used

Process Server

• Dual Xeon @ 2.8GHz with 2G RAM
• Windows XP Professional
• Intalio|BPMS 5.x deployed on Apache Geronimo 1.1.1
• Sun Java Development Kit (JDK) 1.5.0_09
• SoapUI 1.6 load-testing tool

Database Server

• Dual Xeon @ 2.40Ghz with 2.5Gb RAM
  
• Ubuntu Linux 6.10 (Edgy)
• MySQL 5.1 (with InnoDB database)
• SCSI subsystem with 2 x 40G 10K RPM disks

Both servers are connected on the same 1-gigabit local area network. The load-testing tool is run on the same machine as the Process Server and based on our measurements does not consume significant CPU resources.

 

Transaction

We define a transaction as the following sequence of activities:

 

1. Receive a web-service request via SOAP/HTTP
2. Perform some business logic and data manipulation
3. Send back SOAP response on the same HTTP connection

 

Current Results

 

• Persistent process: 3.6M transactions/day
• In-memory process: 14.3M transactions/day

 

We will update this page with more complex transactions and usage scenarios in the future.