From rhauch at redhat.com  Tue Sep  8 10:29:14 2009
From: rhauch at redhat.com (Randall Hauch)
Date: Tue, 8 Sep 2009 09:29:14 -0500
Subject: [dna-users] JBoss DNA 0.6 status
Message-ID: <AC3F2ECE-91A1-4E8F-988F-0CEB05F19766@redhat.com>

Here's a quick status on our 0.6 effort.  In short, we've very close -  
there are only two outstanding issues:

DNA-505 SVN Repository Source with NPE and other issues while opening  
connection through JCR
DNA-513 REST server does not correctly encode binary values

The first issue is already coded and committed to trunk, and ideally  
I'd like to have feedback before closing (though lacking that I will  
mark the issue as resolved at the end of the day).  We've started on  
the second issue and I hope we can resolve that as well today.  Then  
it's just a matter of building and verifying the release.

So please stay tuned.  As usual, if you have any comments or  
questions, feel free to reply here or in the #jbossdna IRC room.

Best regards,

Randall



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/dna-users/attachments/20090908/b1d61c65/attachment.html 

From rhauch at redhat.com  Sun Sep 13 21:55:58 2009
From: rhauch at redhat.com (Randall Hauch)
Date: Sun, 13 Sep 2009 20:55:58 -0500
Subject: [dna-users] Announcing JBoss DNA 0.6
Message-ID: <DE7E2124-5769-46A4-B2E1-7CBAD687E94E@redhat.com>

We've just released version 0.6 of JBoss DNA.  This release brings a  
lot of fixes and a number of really great new features.  We've  
actually done a fair amount of additional integration, and we're  
getting great feedback from our user community.  Thanks to all the  
JBoss DNA team for all the hard work!

Check out our recent blog post for more details about the release, the  
new features (including the new Infinispan connector!), and what's  
coming next.

http://jbossdna.blogspot.com/2009/09/announcing-jboss-dna-06.html

Give it a try, and let us know what you think!

Best regards,

Randall

From apestel at redhat.com  Tue Sep 29 14:14:20 2009
From: apestel at redhat.com (Aaron Pestel)
Date: Tue, 29 Sep 2009 13:14:20 -0500
Subject: [dna-users] Minimum system requirements for using DNA
Message-ID: <4AC24E7C.4020706@redhat.com>

Hello,

Looking for minimum system requirements (RAM, Hard drive space, and CPU 
usage) for using DNA.

We're not looking to actually install on the minimum machine, but need 
to have documentation on what the minimum requirements are.

Thanks!

Aaron Pestel
214.395.1483 (cell)


From rhauch at redhat.com  Tue Sep 29 18:12:46 2009
From: rhauch at redhat.com (Randall Hauch)
Date: Tue, 29 Sep 2009 17:12:46 -0500
Subject: [dna-users] Minimum system requirements for using DNA
In-Reply-To: <4AC24E7C.4020706@redhat.com>
References: <4AC24E7C.4020706@redhat.com>
Message-ID: <06656337-4050-4BC8-905E-3FAE70415BFD@redhat.com>

We have not done any benchmarking to obtain actual measurements with  
different configurations.  So all I can offer at this time are rules  
of thumb.  In short, the better the machine, the easier it will be.   
But please keep in mind that JBoss DNA is actually a pretty  
lightweight system, and I suspect the content will very soon outweigh  
the overhead of the JBoss DNA engine.

The minimum requirements are pretty low, especially when compared with  
the minimums for the JRE.  The only disk space that is required is  
that necessary for the JAR files, and any room for persistent storage  
(e.g., local or embedded database, files, etc.) would have to be added  
to this.  Similarly, the only RAM required is that necessary to run  
the JRE plus hold the JcrEngine and repository objects in memory.  Of  
course, the OS's virtual memory configuration will also influence the  
disk space and RAM requirements.

Needless to say that the practical minimums are almost entirely driven  
by the JBoss DNA configurations: the number of repositories, the  
number of node types, the number of namespaces, the number of  
repository sources, how those sources manage their state (e.g., in- 
memory sources keep it in memory, whereas JPA repository sources might  
persist in a local database and may use Hibernate's second-level  
cache, etc.).  But these metrics will also depend very much on how the  
JCR clients are written: how many concurrent sessions are open, how  
much information is  cached in each session, how much information is  
changed between calling 'save(), and whether the JCR clients hold onto  
the nodes obtained from sessions.  (The latter, btw, shouldn't be too  
bad, as the objects that are returned outside of the JCR interfaces  
are essentially flyweights, and we've carefully designed the system so  
that clients holding onto these objects should not affect how the  
sessions manage their own memory.)

As for CPUs and hard drive (speed), I think the basic rule is "the  
faster, the better".

The surest way to identify the minimums are to test JBoss DNA running  
with a representative configuration and a representative amount of  
content.

Best regards,

Randall

On Sep 29, 2009, at 1:14 PM, Aaron Pestel wrote:

> Hello,
>
> Looking for minimum system requirements (RAM, Hard drive space, and  
> CPU
> usage) for using DNA.
>
> We're not looking to actually install on the minimum machine, but need
> to have documentation on what the minimum requirements are.
>
> Thanks!
>
> Aaron Pestel
> 214.395.1483 (cell)
>
> _______________________________________________
> dna-users mailing list
> dna-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/dna-users


