Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A25D711DE2 for ; Fri, 4 Apr 2014 02:58:43 +0000 (UTC) Received: (qmail 10783 invoked by uid 500); 4 Apr 2014 02:58:42 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 10402 invoked by uid 500); 4 Apr 2014 02:58:41 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 10394 invoked by uid 99); 4 Apr 2014 02:58:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2014 02:58:40 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.82.251.15] (HELO mail1.bemta12.messagelabs.com) (216.82.251.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2014 02:58:35 +0000 Received: from [216.82.249.212:36232] by server-15.bemta-12.messagelabs.com id E9/09-00481-7CF1E335; Fri, 04 Apr 2014 02:58:15 +0000 X-Env-Sender: Ken.Knudsen@imaginecommunications.com X-Msg-Ref: server-3.tower-219.messagelabs.com!1396580294!3872380!1 X-Originating-IP: [70.105.69.14] X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=imaginecommunications.com,-,- X-VirusChecked: Checked Received: (qmail 23018 invoked from network); 4 Apr 2014 02:58:14 -0000 Received: from unknown (HELO VEREXCH02.harrisbroadcast.com) (70.105.69.14) by server-3.tower-219.messagelabs.com with AES128-SHA encrypted SMTP; 4 Apr 2014 02:58:14 -0000 Received: from VEREXCH01.harrisbroadcast.com ([169.254.1.163]) by VEREXCH02.harrisbroadcast.com ([169.254.2.68]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 22:57:51 -0400 From: "Knudsen, Ken" To: "user@couchdb.apache.org" Subject: RE: Bench marking a simple 10k write Thread-Topic: Bench marking a simple 10k write Thread-Index: Ac9Pr0cgbVXwmsKWRg+YTAOIHTohpwAIj7CAAAgrkOA= Date: Fri, 4 Apr 2014 02:57:50 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.96.12.33] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org System is Windows, 64 bit, V-7... With delayed_commits on: roughly 40 seconds for 10k With delayed_commits off...don't ask, way to long. Why I'm asking (as I've asked in IRC as well).... So why am I doing this... well, the Gods that be don't believe NoSQL (Mong= oDB, CouchDB, ArangoDB and so on) can compete with SQL Server.. 10k SQLSer= ver writes get's done in 8 seconds ...pretend there's nothing else you cou= ld convince them of until you show them that 10k writes in CouchDB can hap= pen as fast.. ArangoDB is extremely fast, as I expected (waitforsync=3Dfalse)... I thoug= ht CouchDB would have been just as fast. -----Original Message----- From: Stanley Iriele [mailto:siriele2x3@gmail.com]=20 Sent: April-03-14 10:46 PM To: user@couchdb.apache.org Subject: Re: Bench marking a simple 10k write Are you tearing down the connection and reestablishing it every time? Or h= ave you played with the TCP_no_delay settings?... Could you define slow an= d maybe post your function minus credentials? On Apr 3, 2014 7:41 PM, "Knudsen, Ken" < Ken.Knudsen@imaginecommunications= .com> wrote: > ....to a CouchDB server....I'm literally just executing a unit test=20 > 10k times that open an HTTP connection, post the data and close...=20 > CouchDB is performing very slowly in this. I thought it'd be very fast. = Any ideas? > > Thanks for the help, > > Ken > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service= . > For more information please visit http://www.symanteccloud.com=20 > ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ___________= ___________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________