ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » File Input Node

Post new topic  Reply to topic Goto page Previous  1, 2
 File Input Node « View previous topic :: View next topic » 
Author Message
kimbert
PostPosted: Thu Feb 05, 2009 2:22 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5543
Location: Southampton

We are taking time to help you, so please take time to respond to the points which we raise.
Quote:
Processing time varies with the size of the file

Yes, of course. But does it vary linearly with the size of the file?
Quote:
But i have another flow with the same type of nodes and it process 4-5MB file in 3-4 minutes, thats what i expect from this flow too
Why do you expect that? Does the other message flow use the same type of MRM message definition? Same message style? Same type of processing in its Compute node ( if it has one )?
Quote:
The code i used earlier to create the output using Refernce for Output.MRM creats a 0 byte file
Then you are (obviously) building a different output message tree. You should use Trace nodes and user trace to find and fix your defect.
Quote:
This technique would seem like a good idea if you are not already doing something similar: http://www.ibm.com/developerworks/websphere/library/techarticles/0505_storey/0505_storey.html
Did you read this? Are you building the entire input tree and holding it in memory?

General advice:
1. Fix your revised code so that it no longer creates 0 byte output. Check the performance ( it might go faster when you have fixed the defect ).
2. Replace the Compute node with a really simple one that creates a tiny output message in the XMLNSC domain. Set Parse Timing to Immediate on the input node. This message flow will test the parsing speed. If it still takes 30-40mins to process the input file, then there is no point in tuning your Compute node ( but the link which I posted might still be useful ).
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » File Input Node
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.