Thursday 24 March 2016

Load test traffic analysis–what goes where

When trying to work out your JD Edwards architecture, you really need to know what goes where – (in terms of network traffic), so you can design disk and network layers appropriately.

Wouldn’t it be nice to understand relative numbers of IO and disk so that you could provision this properly.  Well, I’m here to help.

When load testing 50 concurrent users with a mixed work load (queries and writes), very busy…  282000 unique JDE pages in 60 minutes.  This generated 2GB of HTML traffic (to and from) the HTML servers.

The traffic analysis between the various tiers is below, but before I get to this… what else do these numbers tell you?

For starters, each session was 11.4KB/s, that is good to know for remote connections.

image

My awesome visio skills are on display above.  Note that the traffic arrows are fairly generic.  You know that webserver OUT = user HTML in + JDBC in + logic calls out….  It’s not just to the end users.  Same with logic server, most traffic to the database server – but quite a bit to HTML.

No comments: