Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 39958 invoked from network); 15 Apr 2008 14:04:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Apr 2008 14:04:01 -0000 Received: (qmail 40262 invoked by uid 500); 15 Apr 2008 14:04:00 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 40246 invoked by uid 500); 15 Apr 2008 14:04:00 -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 40237 invoked by uid 99); 15 Apr 2008 14:04:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2008 07:04:00 -0700 X-ASF-Spam-Status: No, hits=3.8 required=10.0 tests=HTML_MESSAGE,MIME_QP_LONG_LINE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of david@smallsolid.com designates 69.89.22.11 as permitted sender) Received: from [69.89.22.11] (HELO outbound-mail-101.bluehost.com) (69.89.22.11) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 15 Apr 2008 14:03:16 +0000 Received: (qmail 25507 invoked by uid 0); 15 Apr 2008 14:03:25 -0000 Received: from unknown (HELO host156.hostmonster.com) (74.220.207.156) by outboundproxy3.bluehost.com with SMTP; 15 Apr 2008 14:03:25 -0000 Received: from wsip-70-167-16-134.ri.ri.cox.net ([70.167.16.134] helo=[192.168.123.110]) by host156.hostmonster.com with esmtpa (Exim 4.68) (envelope-from ) id 1Jllkr-0002DE-AU for users@jackrabbit.apache.org; Tue, 15 Apr 2008 08:03:25 -0600 Message-Id: From: David Parker To: users@jackrabbit.apache.org In-Reply-To: <03f301c89efa$b72a3b70$257eb250$@co.uk> Content-Type: multipart/alternative; boundary=Apple-Mail-15-180255919 Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: Scalability of using "reference" properties Date: Tue, 15 Apr 2008 10:03:26 -0400 References: <03f301c89efa$b72a3b70$257eb250$@co.uk> X-Mailer: Apple Mail (2.919.2) X-Identified-User: {686:host156.hostmonster.com:smallsol:smallsolid.com} {sentby:smtp auth 70.167.16.134 authed with david+smallsolid.com} X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-15-180255919 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Could you provide a pointer to the to the data modeling tips you =20 mentioned? - DAP On Apr 15, 2008, at 9:14 AM, sbarriba wrote: > Hi all, > Last year David Nuescheler provided some very useful data modelling =20= > rules =96 1 of which related to the use of =93reference=94 properties. > > We had various, reasonable, use cases for which we felt references =20 > were appropriate e.g. to ensure referential integrity. While =20 > semantically they=92ve worked well for us, as our repositories grow in = =20 > size we=92re now seeing how expensive references can be where you have = =20 > 1,000=92s of items referencing the same node. Monitoring our SQL logs =20= > (on MySql) we can see some pretty huge database operations which are =20= > getting incrementally slower as more and more items reference a node. > > Ignoring the data modelling semantic of using =93reference=94 = properties =20 > for the moment, is there anything that can be done in order to =20 > improve the performance of references or do you always have to =20 > design with this limitation in mind (hindsight being very useful)? > > We=92re facing a tricky remodelling/migration exercise to ensure =20 > further scalability. > > Regards, > Shaun > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D David Parker david@smallsolid.com (401) 263-1782 --Apple-Mail-15-180255919--