Arch2Arch Tab BEA.com
Syndicate this blog (XML)

'Event-transformers' Turbo charge your Event Processing EDA solutions

Bookmark Blog Post

del.icio.us del.icio.us
Digg Digg
DZone DZone
Furl Furl
Reddit Reddit

Robin Smith's Blog | November 11, 2007  10:59 PM | Comments (0)


The WebLogic® Event Server was released this summer, as the very first and only Event Processing “Application” Server based on the BEA microServices Architecture, focused on delivering the real power of Complex Event Processing coupled with extreme low latency and high event through-put.

The whole essence of this complete Event Processing ‘middleware’ solution is that BEA has, and will continue to leverage the very latest technologies such as its unique deterministic JVM garbage collection features and a highly tuned Java container with an OSGi backplane.

Created from the ground up with an OSGi modular framework every aspect of the product has been built for performance through-put, but at the same time still ensuring application latencies in the sub-millisecond range. In addition to a wealth of configurable and programmable capabilities,  this Java runtime and container is the ideal solution for organizations that need a scaleable Event Processing implementation.

As more and more Companies adopt these new products and gain the major advantages possible from this kind of implementation, the team at BEA has been very committed to ‘stressing’ the new Java Container and the unique Java Runtime (WebLogic® Real Time) to understand just some of performance speeds possible, by scaling its capabilities with a fairly typical use case for high event through-put performance. Of course, there are many different kinds of implementations possible around Event Processing, and we suspect the high performance possibilities of our advanced solution may be limitless, but we want to provide a foundational information base for companies now who want to evaluate purely at the performance level.

So recently, in the BEA performance labs (the result being formally published in a new BEA whitepaper ) , the team implemented a financial services benchmark testing scenario to identify a ‘low tide’ benchmark level for latency and event through-put that can be achieved.

The monitored application was not just a simple event “pass-through” type of example, where no ‘real’ CEP is performed that provides just t a façade of high numbers but has no real value for enterprise strength solutions. This scenario implemented around 400 pattern matching queries on the inbound data stream with significant high complexity. One of the major 'configurability' capabilities of the WebLogic Event Server can be observed in the way parallel processing is achieved by enabling multiple container connections to be introduced.

The resulting statistics were amazing, as the load generator ramped up the message injection rate to over 200 thousand events per second, the latencies were less than 50 microseconds, and with over 1 million events per second only around 69 microsecond latency, this is just an indication of the extreme processing power of the Event Server.

Below is a graph showing just some of the results, but to get all the details, I highly recommend you review the complete whitepaper from the BEA website.

perf.wp.the.scenario.graph.Avg.latency.vs.injection.rate.10.connections

Together with the ability to meet and exceed an Enterprise goals in terms of performance, there is also a need for Visualized Event Processing Network monitoring, providing the capability to instantly identify these through-puts and latencies for each node.

So not only does the WebLogic Event Server provide a comprehensive JMX framework for users to interact and extract the information programmatically, but BEA is launching soon a new value-add diagnostic focused feature which visually and graphically exposes these interfaces in many ways to review and analyze the activity of executing Event based applications.

Using this component, the WebLogic Event Server Monitoring Dashboard, you can easily identify the Applications which are executing in an Event Server instance and the performance of the associated EPN nodes (Adapters, Streams and Processors).

Historical analysis around the performance of EDA applications is aided with some nice features, such as the PDF report generation option, which will enable developers to record and study the effects of changes to their applications as they implement different features and EPL queries.

The Monitoring dashboard must be installed with the WebLogic Event Server 2.0 base product and will form the foundation for other ‘cool’ new visual diagnostic tools, joining a ‘family’ of a new breed of Event Server tooling from BEA, which will provide a wide range of capabilities addressing the needs of EDA developers, Architects and Business users.

monitoring.dashboard

For more information on the Monitoring dashboard, I recommend that you look at the screencast available on dev2dev.bea.com.


Comments

Comments are listed in date ascending order (oldest first) | Post Comment



Only logged in users may post comments. Login Here.

Powered by
Movable Type 3.31