I'd love some examples of 'what not to do in the real world' so I can simulate high memory and/or cpu.  Huge XML messages with a CopyEntireMessage procedure in a load test just isn't cutting it.  I'm thinking infinite loops, poorly coded procedures, really anything that would kill the performance of a flow.  

I'm running ACE 12 lts on OpenShift and am using a Quick Start integration server (368mb memory, .3 cpu).  At the moment I'm looking to test HPA from an infrastructure side and am not really an ESQL developer.  Any help on what not to do in real life, so I can get some pretty poor performance would be greatly appreciated.  Extra points for creativity!

Matt

If your purely wanting to test out HPA then we provide a tool in our documentation - https://www.ibm.com/docs/en/app-connect/containers_cd?topic=ayisir-configuring-vertical-pod-autoscaling-integration-server-integration-runtime-pods#vpainaction__title__1

That's exactly what I need, thanks Rob!

Matt, I don't have the code in ACE, but expect it could be easily replicated. A long ago project had uncovered an MQ client app, receive a single message, perform a DB lookup, then use the result set of the query to generate emails & individual response messages. When the result set generated over 50k responses within a single unit of work, bad things were happening. 

Thanks Dean.  I think Rob has us covered with the linked bar, but I'll reach out if it doesn't work as expected.