From users-return-12264-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri Aug 14 04:35:37 2009 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 52479 invoked from network); 14 Aug 2009 04:35:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Aug 2009 04:35:37 -0000 Received: (qmail 46379 invoked by uid 500); 14 Aug 2009 04:35:43 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 46329 invoked by uid 500); 14 Aug 2009 04:35:43 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 46318 invoked by uid 99); 14 Aug 2009 04:35:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 04:35:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nigel.sim@gmail.com designates 74.125.78.26 as permitted sender) Received: from [74.125.78.26] (HELO ey-out-2122.google.com) (74.125.78.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 04:35:34 +0000 Received: by ey-out-2122.google.com with SMTP id 4so257592eyf.13 for ; Thu, 13 Aug 2009 21:35:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=yIvoy/nTrmyyHaMAr95r+lBTAJxBFxBZKnEdxH1UOrs=; b=NrkkVwzX+wqs5VfIKeqTXvKikLU4aHdb5rBjvqOTZxWPtrq8D1Y4LJraso8Hx3E6Gw TzHdsx+zmFtC/V860IN1Das0Ch3KhZzW4pVhQRGOaya9UEe62d8Qv0St0VO9gIQ3mXJI zPA74dACjcYcwDrlYJGa3UWHlrpb4P7wlzPjs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=u/oJD9YSjzp5TTRO8PGQ8sZygeSriEBfdo3tGqlhjycDn9MeC07ovTXBV68hQo3G5z pH32uh1jF69MPMrebAAJBjAJcVnr1e/S33WxdGD5NF9icxWId4hsD867+lp56l8uc2U2 qN7ohUZ7Y2Br+E1OrlWBXJTxz2tk7/vGTMqZo= MIME-Version: 1.0 Received: by 10.210.89.7 with SMTP id m7mr2533149ebb.92.1250224514067; Thu, 13 Aug 2009 21:35:14 -0700 (PDT) From: Nigel Sim Date: Fri, 14 Aug 2009 14:34:54 +1000 Message-ID: <5bab330d0908132134o68cd9089iacb5cd0a1372d923@mail.gmail.com> Subject: Performance of a large number of small nodes To: users@jackrabbit.apache.org Content-Type: multipart/alternative; boundary=0015174be8740cedd9047112942c X-Virus-Checked: Checked by ClamAV on apache.org --0015174be8740cedd9047112942c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I am using Jackrabbit to store a mixture of scientific data, which includes files and numerical data. The performance of files are fine, but the numerical data needs to be extracted as datasets based on attributes such as observation time, and this appears to be quite slow in comparison to a native DB (obviously). I would really prefer to keep all this related data in the same management system, so is there a way to improve the ingestion and retrieval of many small nodes? Perhaps I could register a certain backend storage type for my numerical nodes which have the same 5 or 6 attributes, and would feel more at home in a single DB table? My second question, is there an efficient way to query for the latest observation? I would assume querying for the node type, sorting, and just retrieving the first result? Cheers Nigel --0015174be8740cedd9047112942c--