Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 68412 invoked from network); 3 Mar 2010 11:06:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Mar 2010 11:06:02 -0000 Received: (qmail 5936 invoked by uid 500); 3 Mar 2010 11:05:55 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 5911 invoked by uid 500); 3 Mar 2010 11:05:55 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 5903 invoked by uid 99); 3 Mar 2010 11:05:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 11:05:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 11:05:46 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NmmOL-0004YM-Ek for users@activemq.apache.org; Wed, 03 Mar 2010 03:05:25 -0800 Message-ID: <27766785.post@talk.nabble.com> Date: Wed, 3 Mar 2010 03:05:25 -0800 (PST) From: dara kok To: users@activemq.apache.org Subject: RE: best approach to transfer large File, modify content on receive In-Reply-To: <0669EB61C3BF9143AF3D7BE84DF29B52C7658061@rocjexm01.endava.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mrpc.cambodia@gmail.com References: <27766358.post@talk.nabble.com> <0669EB61C3BF9143AF3D7BE84DF29B52C7658061@rocjexm01.endava.net> X-Virus-Checked: Checked by ClamAV on apache.org So you think sending the file in full size is not performance efficient? I wonder what happens when the receiving app get the file, will the full content of the file load into memory or will just part of it will get loaded and the rest will load on demand? Thanks, Can you chunk the file? In this case you might split it between multiple producers and consumers and play with the number of producers/consumers and chunck size. You may send and process chuncks concurrently and also limit the message size. Just one option... -- View this message in context: http://old.nabble.com/best-approach-to-transfer-large-File%2C-modify-content-on-receive-tp27766358p27766785.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.