Someone asked me to do some performance measurements on the use of selectionstrings (so you can say give me the next message with the following message properties).
We have had some discussions about the best way of reporting the information. It is very easy to provide lots of data - but not information, so I thought I would ask people - you - for any preferences.
When you look at performance data what are you looking for? I think it is questions like
- If I use messages properties - how much will CPU increase ( and so will I run out of CPU)
- If I use a selectionString - how much does this cost me.
- If I have to skip 1000 messages to find a message which matches the selectionString - how much does it cost/
I dont think you want information on persistent and non persistent ( as it should be similar) nor do you want a range of message sizes, eg 1KB 5KB 10KB 50 KB etc is this true?
Distributed produce graphs of CPU cost vs number of subscribers. Is this helpful.
For me the fewer data points I have to produce the better it is for me, as it takes less time. Too much work, and I wont have time to do it - so you get nothing.
So please give me your comment - either add them to this blog - or email them to me PAICE@UK.IBM.COM.
I'll post a summary of any answers I get .
- What is the impact on throughput?
- What are the known bottlenecks?
- What are the best practices?