Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of mueller@adobe.com designates
 64.18.1.35 as permitted sender)
From: Thomas Mueller <mueller@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Thu, 28 Jun 2012 16:00:47 +0100
Subject: Re: Updated Oak roadmap
Thread-Topic: Updated Oak roadmap
Thread-Index: Ac1VPtDO5aXmfTMtQEStLZCUXu38Eg==
Message-ID: <CC123D5F.2EF71%mueller@adobe.com>
In-Reply-To: 
 <CAOFYJNaj4i+Hug1VfoXX0t7z+HS40s0uQ=joRHY6AaPT=D_GiQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

>Yes, we can do such a benchmark (the oak-bench component already has
>the basics in place), though personally I don't see the single-node
>case as a particularly interesting one to benchmark. Unless we want to
>also target embedded systems, any truly performance-critical
>deployments will probably in any case be clustered.

Well, I think what is available in the Oak project should also be
performant, so we should test for it... According to the stated goals in
the pom.xml and Oak web site:

    "The goal of the Oak effort within the Apache Jackrabbit=81 project is
    to implement a scalable and performant hierarchical content repository
    for use as the foundation of modern world-class web sites and other
    demanding content applications."

If that's not the case, then we should change the web site and the pom.xml
accordingly.

Regards,
Thomas