Tuning WCS Developer Toolkit

Posted by Hariharan Vadivelu on
In addition to increasing the JVM heap size, you can perform few more tuning to developer toolkit to improve the performance of development tookit.

Refer to my previous blog on tuning the developer toolkit JVM heap Size.
http://techhari.blogspot.com/2009/10/websphere-commerce-toolkit-out-of.html

Tuning Apache Derby Database
------------------------------------------


Derby is a filesystem based database, there are few minor configuration changes that can be
performed on the toolkit Derby properties to improve overall performance of the Commerce Developer Toolkit.

The file is located in following location for WCS V7
\SDP\runtimes\base_v7\derby\derby.properties


With this Derby will be able to access data from cache instead of filesystem, this will reduce overall I/O as data will be read from the cache.

Set derby.storage.pageCacheSize = 10000
Set derby.storage.pageSize = 8192

Refer to following link for Apache Derby tuning


http://db.apache.org/derby/docs/dev/tuning/tuningderby.pdf

Enabling Distributed Cache
-------------------------------------



Enable distrubutemap cache for OOB objects, this will improve the performance by caching OOB data and avoiding DB roundtrips.

Copy WCDE_ENT70\samples\dynacache\cacheinstances.properties to
WCDE_ENT70\workspace\Stores\src\

Refer following link for the list of OOB Distributed Cache Map.

http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.admin.doc/refs/rdclogcachnameDM.htm

2 comments: