Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 76210 invoked from network); 8 Sep 2006 13:57:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Sep 2006 13:57:33 -0000 Received: (qmail 8612 invoked by uid 500); 8 Sep 2006 13:57:32 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 8584 invoked by uid 500); 8 Sep 2006 13:57:31 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 8573 invoked by uid 99); 8 Sep 2006 13:57:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 06:57:31 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.42.27] (HELO nwkea-mail-5.sun.com) (192.18.42.27) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 06:57:30 -0700 Received: from phys-epost-1 ([129.159.136.14]) by nwkea-mail-5.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k88Dv9sq005302 for ; Fri, 8 Sep 2006 06:57:10 -0700 (PDT) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0J5A00F011B0WQ@epost-mail1.sweden.sun.com> (original mail from Andreas.Korneliussen@Sun.COM) for derby-user@db.apache.org; Fri, 08 Sep 2006 15:57:09 +0200 (MEST) Received: from [129.159.112.247] (khepri35.Norway.Sun.COM [129.159.112.247]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPA id <0J5A00FTY1F8AP@epost-mail1.sweden.sun.com> for derby-user@db.apache.org; Fri, 08 Sep 2006 15:57:09 +0200 (MEST) Date: Fri, 08 Sep 2006 15:57:02 +0200 From: Andreas Korneliussen Subject: Re: Large BLOBs In-reply-to: <45011FC0.8050201@intland.com> To: Derby Discussion Reply-to: Andreas.Korneliussen@Sun.COM Message-id: <450176AE.10403@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=------------enigB5345557CBFB5CC4EFFACDBB User-Agent: Thunderbird 1.5.0.5 (X11/20060730) X-Enigmail-Version: 0.94.0.0 References: <45011FC0.8050201@intland.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --------------enigB5345557CBFB5CC4EFFACDBB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Robert Enyedi wrote: > We are planning to use Derby for a database that has large BLOB files > around 50-60 MB. Can Derby handle such large amount of data by default > or should we think about certain server configuration changes? >=20 By default, derby can handle such large amount of data. The network client will, when fetching a BLOB, load the entire BLOB into memory. The network server, when receiving a BLOB from client, will also load it into memory before inserting it into the db. This means that you probably need to increase the max heapsize of the VM to avoid OutOfMemory errors, or restrict usage to embedded mode. Regards Andreas > Regards, > Robert --------------enigB5345557CBFB5CC4EFFACDBB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAXa036DpyYjYNyIRAkg8AJ9Q+nwlqNsDJVPUXDH7o53S5Rf/oQCglwET 0Qil8IlH22nfnw+cvBsp6uA= =jSw2 -----END PGP SIGNATURE----- --------------enigB5345557CBFB5CC4EFFACDBB--