| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Slow debugger |
« View previous topic :: View next topic » |
| Author |
Message
|
| KIT_INC |
 Posted: Fri Jul 23, 2010 7:12 am Post subject: Slow debugger |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Is there anyway to speed up the debugger ? I am running WMB V61 on Windows XP. My debugger is really slow. I did not notice this before when I was debugging flows using MQ nodes My message flow is simple FileInput -- Compute --- FileOutput. The file size is about 2.5M. XMLNSC is the parser used. I have break point set up just before the compute node and inside the ESQL code. It takes about 10 second for the FileINput node to pick up and parsed the file to produce the XMLNSC tree in the debugger which I think is fine. But stepping into the compute node and single stepping through the ESQLs takes more than 15 seconds for each step. This make debugging almost impossible. I looked at my task manager, System Idle Process is 99% CPU most of the time. Is there anyway to check what has gone wrong ? |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Fri Jul 23, 2010 7:31 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
whats your RAM size...Debugger usually eats the memory...
my advice is to go for user trace, easy, and pretty well to understand, and answers you why, what and when questions
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Mon Jul 26, 2010 4:55 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| I have 2 G of RAM. It seems ok when debugging with MQ messages which is normally 10 to 20K in length. It may be because of the file is 2.5M. But I thought once it is parsed into a tree, the debug should be fine. It may take time to go through the tree because of size. But should not take 10 - 15 seccond each step. I'll use trace instead. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jul 26, 2010 5:52 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
A couple of things that helped me:
1. I ran msconfig (start button -> run -> type msconfig ) and unchecked all unneeded programs. It surprised me how much gobbledegook of wasted CPU and memory junk programs were running without my explicit consent. Under the "Startup" tab from msconfig, all these additional programs were being run at startup without any benefit to me. By the way, you need to be local admin on your laptop to run this. Uncheck the programs you do not need at startup and click OK, then reboot.
2. Sometimes we install more than one Broker Execution Group on your laptop. These eat up CPU and memory because they start at system boot time. Start button -> Control Panel -> Administrative Tools -> Services -> "IBM Message Broker Component xxxExecutionGroup" -> Properties -> set Startup type to manual on all of your execution groups. Then manually start the one you want later, after boot time.
3. On very rare occasion, I accidentially have duplicate message flows running in separate execution groups. This causes debugger delay.
4. Internet explorer -> tools -> internet options -> programs -> manage add ons -> delete anything you don't use. Lots of garbage gets loaded into memory and chews up CPU and other resources when you browse websites.
5. Start button -> control panel -> Add or remove programs. Again, get rid of the junk you never use.
6. Never use hibernate mode. Always start with a fresh reboot every morning.
7. Reboot at lunch time.
Good luck.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
