Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 72655200BDD for ; Sat, 26 Nov 2016 02:38:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 710AF160B1D; Sat, 26 Nov 2016 01:38:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B6DFC160B1C for ; Sat, 26 Nov 2016 02:38:08 +0100 (CET) Received: (qmail 86700 invoked by uid 500); 26 Nov 2016 01:38:07 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 86231 invoked by uid 99); 26 Nov 2016 01:38:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Nov 2016 01:38:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 36AC91A0154; Sat, 26 Nov 2016 01:38:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.899 X-Spam-Level: * X-Spam-Status: No, score=1.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Kh-yaBR8qg5q; Sat, 26 Nov 2016 01:38:04 +0000 (UTC) Received: from mail-pf0-f171.google.com (mail-pf0-f171.google.com [209.85.192.171]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 70D655F2F2; Sat, 26 Nov 2016 01:38:04 +0000 (UTC) Received: by mail-pf0-f171.google.com with SMTP id d2so16662134pfd.0; Fri, 25 Nov 2016 17:38:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t/czvEboa0qjV4reY31r62t6q98DntSR0oJAuTizzdg=; b=RxuXu9cWWeEtRUhGQO9o7q0kdIS5XqaPX44XcEt/ylvqutQvYe6iNytuibAL5hlq8S KO0/rKErXwSC+TlB5hNxv3AH55cicIzEUUyzF1wz8lM/Y1XM40YM9P9Oya6CpM96cZlf Or93/oUVni53iKEZ5031+q0yFcOMG9XBegKLOAbLoICLfOW7DcvxooEfaJS0uRj+NYjW ATGGcnWlI3NCpLi6UQ8UmGkaVhqVki5vmlZzVpkvPIe5oy4XpbY4c3aCQ2MTl+tOhIo/ FvL7FFLXK0L0dcRNu4o0vJ2a11wLTg55qhusLEsGujG6sPGB4Ep8/iZ2ObN4S+KfFctB hN+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t/czvEboa0qjV4reY31r62t6q98DntSR0oJAuTizzdg=; b=LCHm1MqdsPiFQrQVvQn59vo4PtML2woPlGsFhAzuYf3aEyoKzSByIhYtm/yUbSw4PR Q9kEv1dfsYx12m2SlWTc0Bn0fd6e5tvPHW3VatcO8gVVVmDYNmZJenyQiuFVG00Xf6C5 BU715d7NEQ0z5CYqavF+UD1UCzZNYq9I7c4XetO7Yo8vif2qlXCMB2jKTbogotRxhXd5 6TUL3C1BhwDdJGCJtfFp6zoQNxh6b6iPl77xxpAwcjJyQinxPNpCwj+GHaCoJf6E5m3F W3eNEC4j99dwXk4Q1beZu81k7pxFL05HVCkUsYWsVGJ9gSI0RsJlRo2h0zMCuwo1Anql 35ew== X-Gm-Message-State: AKaTC03XeB9v2OFmnvUvhyW8yOg2aNr+8X8PhWGc+2gCaIK6ZuNa5k+FKrAaOxVSyJO/pQ== X-Received: by 10.84.210.40 with SMTP id z37mr23936220plh.32.1480124276288; Fri, 25 Nov 2016 17:37:56 -0800 (PST) Received: from [10.137.194.117] (vpn-sfbay-198-11-218-35.hosts.getcloakvpn.com. [198.11.218.35]) by smtp.gmail.com with ESMTPSA id g27sm44207971pfk.58.2016.11.25.17.37.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Nov 2016 17:37:55 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-EC0D26EB-43FF-4838-8856-92728763E62E Mime-Version: 1.0 (1.0) Subject: Re: Nifi Capability for Fast transfer of Data From: Andy LoPresto X-Mailer: iPhone Mail (14B72c) In-Reply-To: Date: Fri, 25 Nov 2016 17:37:55 -0800 Cc: users@nifi.apache.org Content-Transfer-Encoding: 7bit Message-Id: <2315C40A-9438-4643-BFC4-9EDC208E6AF6@gmail.com> References: To: dev@nifi.apache.org archived-at: Sat, 26 Nov 2016 01:38:09 -0000 --Apple-Mail-EC0D26EB-43FF-4838-8856-92728763E62E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Unless my back of the envelope math is way off, to transfer 50GB (400Gb) per= second, you would need 40 parallel 10GbE connections, assuming absolutely n= o overhead. Your precision for "a few seconds" would need to be 40+ seconds u= sing a single 10 GbE link and optimal transmission speed.=20 =46rom the Apache NiFi Overview document:=20 "for something concrete and broadly applicable, consider the out-of-the-box d= efault implementations. These are all persistent with guaranteed delivery an= d do so using local disk. So being conservative, assume roughly 50MB per sec= ond read/write rate on modest disks or RAID volumes within a typical server.= NiFi for a large class of dataflows then should be able to efficiently reac= h 100MB per second or more of throughput. " Those numbers are at least 18 months old, so with a robust cluster of 8 high= -performance machines and an optimized flow to balance computation across al= l the boxes, I would ballpark a perfect world estimate at 1Gbps. My last kno= wledge of HDFS write speeds was around 10-20Gbps. Again, if your tolerance f= or the full process is 40-50 seconds, NiFi should be able to keep up, but yo= ur uplink will probably be the long pole in the tent here.=20 Feel free to correct any poor assumptions or bad math above.=20 Andy LoPresto alopresto@apache.org alopresto.apache@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Nov 24, 2016, at 20:48, shweta Aggarwal wrot= e: >=20 > Hi folks, >=20 > We have a requirement in one of our time critical application wherein we > are looking for transferring upto 40-50 GBs worth images > within few seconds between remote machine and HDFS. >=20 > Assuming network connectivity between the two is on a 10Gbe link and NIC > and socket buffers tuned optimally to give best performance , does Nifi > have a capability to support desired performance using a combination of > "getFile" and "putHDFS" on a high ended cluster of >8 nodes. >=20 > We are also exploring a combination of HDFS+GrdiFTP for fast transfer of > images from remote machine to HDFS cluster. >=20 > Any thoughts or pointers shall be helpful. >=20 > Thanks!! --Apple-Mail-EC0D26EB-43FF-4838-8856-92728763E62E--