MQSeries.net :: View topic

goffinf · Posted: Thu Feb 22, 2007 7:35 am Post subject:

Devlopment Environment:

WBIMB v6
Windows 2003 Server (VMWare image - 2GB memory)

We have been using Message Broker quite happily in this VMWare environment for quite some time and in general performance whilst developing flows and running debug is pretty reasonable.

Of late performance has slowed down a lot. It doesn't appear to be CPU but lots of disk thrashing. This happens when the Broker and DB Instance are started and at random intervals things slow up causing the machine to freeze for a short length of time.

We also notice an extremely long wait time to open a bar file (often 3/4 minutes) and deploying that bar (2/3 minutes). Again the CPU is quiet enough. The bars are typically around 5MB. Debug can also be a bit of a trial

- unstable and doesn't always stop on breakpoints particularly if they are in eSQL.

This *may* be an issue completely unrelated to Message Broker, but I was just wondering whether there are any logs or temp directories or queues that might 'fill up' and would benefit from a bit of housekeeping or whether the config database should be reorg'd regularly or anything else that anyone can think of that might be symptomatic ??

Cheers

Fraser