ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <rwhee...@artifact-software.com>
Subject Re: using H2 database for accelerated development
Date Mon, 21 Sep 2015 21:41:46 GMT
If you don't have an SSD but have some spare ram, you might put your DB 
on a ramdrive if it is not too large.

I have not tried this but run Eclipse and the Java compiler off a 
ramdrive and that helps a lot - faster than an SSD but I only have a 2GB 
RAMDrive so it is not a huge place to play.

Ron

On 21/09/2015 5:26 PM, Adrian Crum wrote:
> Before switching databases, you could try tweaking the entity engine 
> settings and the log settings.
>
> Here is a diff of changes that work well for me:
>
> Index: framework/base/config/log4j2.xml
> ===================================================================
> --- framework/base/config/log4j2.xml    (revision 1704346)
> +++ framework/base/config/log4j2.xml    (working copy)
> @@ -40,6 +40,7 @@
>          </Async>
>      </Appenders>
>      <Loggers>
> +        <logger name="org.ofbiz.entity.jdbc.DatabaseUtil" level="warn"/>
>          <logger name="org.ofbiz.base.converter.Converters" 
> level="warn"/>
>          <logger name="org.apache" level="warn"/>
>          <logger name="freemarker" level="warn"/>
> Index: framework/entity/config/entityengine.xml
> ===================================================================
> --- framework/entity/config/entityengine.xml    (revision 1704346)
> +++ framework/entity/config/entityengine.xml    (working copy)
> @@ -165,6 +165,7 @@
>              use-indices-unique="false"
>              alias-view-columns="false"
>              use-order-by-nulls="true"
> +            max-worker-pool-size="-1"
>              offset-style="fetch">
>          <read-data reader-name="tenant"/>
>          <read-data reader-name="seed"/>
> @@ -220,6 +221,7 @@
>              use-pk-constraint-names="false"
>              use-indices-unique="false"
>              alias-view-columns="false"
> +            max-worker-pool-size="1"
>              use-order-by-nulls="true">
>          <!-- beware use-indices-unique="false" is needed because of 
> Derby bug with null values in a unique index -->
>          <read-data reader-name="tenant"/>
> @@ -249,6 +251,7 @@
>          use-pk-constraint-names="false"
>          use-indices-unique="false"
>          alias-view-columns="false"
> +        max-worker-pool-size="1"
>          use-order-by-nulls="true">
>          <read-data reader-name="tenant"/>
>          <read-data reader-name="seed"/>
>
> Creating the database and loading demo data takes about a minute. 
> Building the whole project from scratch takes about 2 minutes.
>
> Having a SSD is a must for laptops.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 9/21/2015 1:42 PM, Gabriel Oberreuter wrote:
>> Hi, I would like to share with guys new to Ofbiz that you can gain 
>> lot of DB
>> related speed using the H2 database rather that the default Derby one.
>>
>> When building the project and creating the databases, on one of our
>> engineers laptop the whole process took about ~15 minutes with Derby, 
>> and
>> switching to H2 reduced that time to about ~3 minutes. That is a lot of
>> time. On my workstation the time went from 3 minutes to ~2. (SSD and 
>> more
>> powerful CPU).
>>
>> This has proven very helpful specially since we are just starting using
>> ofbiz and need to create the db lots of times.
>>
>> Just for your info.
>>
>>
>>
>> -- 
>> View this message in context: 
>> http://ofbiz.135035.n4.nabble.com/using-H2-database-for-accelerated-development-tp4672568.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


Mime
View raw message