Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change 
notification.

The following page has been changed by JörnNettingsmeier:
http://wiki.apache.org/lenya/How_to_tune_Lenya_2%2e0_for_Production_Use

------------------------------------------------------------------------------
  ## page was renamed from How to tune Lenya 1.4 for Production Use
- '''Note:''' The content of this page has been added to the documentation. 
Please update the documentation if you make any changes.
+ '''Note:''' The old content of this page has been added to the documentation 
at http://lenya.apache.org/docs/2_0_x/tutorials/production.html. This page is 
now empty to avoid duplication. Feel free to add stuff that's missing from the 
web docs, and if you transfer new stuff from here into the web docs, delete it 
as well.
  
- ----
- 
- When you check out the SVN trunk to try Lenya 2.0, you will get a setup that 
is geared towards development and debugging, and is thus not well suited to 
production use in many aspects. This page gathers some information about making 
an installation from trunk ready for some serious work.
- 
- == Debugging ==
- 
- Disable the "debug" in src/targets/properties-build:
- {{{
- @@ -48,7 +48,7 @@
- -  <property name="debug"          value="off"/>
- +  <property name="debug"          value="on"/>
- }}}
- 
- Change logging to either error or fatal to prevent the log file from reaching 
very large sizes quickly. In 
externals/cocoon_2_1_x/src/webapp/WEB-INF/log4j.xconf or ultimately 
build/lenya/webapp/WEB-INF/log4j.xconf 
- {{{
-    <root>
-      <priority value="error" />
-      <appender-ref ref="COCOON_DEFAULT" />
-    </root>
- }}}
- 
- == Cache ==
- 
- The default store implementation in cocoon is an in-memory store backed by a 
disk store (based on EHCache). You can configure this store 
- using a file called ehcache.xml which is located in 
''org/apache/cocoon/components/store/impl/ehcache.xml''.
- The default entries of the defaultCache are as follows: 
- {{{
-     <defaultCache
-         maxElementsInMemory="10000"
-         eternal="true"
-         timeToIdleSeconds="0"
-         timeToLiveSeconds="0"
-         overflowToDisk="true"
-         diskPersistent="true"
-         diskExpiryThreadIntervalSeconds="120"
-         />
- }}}
- So, when overflow-to-disk is set to true, eternal to true and 
- timeToIdleSeconds=0, then once a cachekey is in memory/disk, it will never be
- removed which might lead to a cache file becoming very large (see also 
thread: http://java2.5341.com/msg/170235.html)
- 
- For production use these setting should be changed. A possible configuration 
might look like: 
- {{{
-     <defaultCache
-         maxElementsInMemory="10000"
-         eternal="false"
-         timeToIdleSeconds="1800"
-         timeToLiveSeconds="3600"
-         overflowToDisk="true"
-         diskPersistent="true"
-         diskExpiryThreadIntervalSeconds="120"
-         />
- }}}
- This cache contains a maximum in memory of 10000 elements, and will expire an 
element if it is 
- idle for more than 30 minutes and lives for more than 60 minutes. If there 
are more than 10000 
- elements it will overflow to the disk cache.
- 
- 
- 
- == Security ==
- 
- Remove the default publication, or (if you're inheriting from it), at least 
change the default passwords.
- 
- == Cosmetics ==
- 
- In order to hide the default publication from the welcome page (if you're not 
going to rewrite it anyway), you can set
- {{{
- --- lenya/src/pubs/default/publication.xml      (revision 452350)
- +++ lenya/src/pubs/default/publication.xml      (working copy)
- @@ -17,12 +17,13 @@
- -<publication xmlns="http://apache.org/cocoon/lenya/publication/1.1"; 
show="true">
- +<publication xmlns="http://apache.org/cocoon/lenya/publication/1.1"; 
show="false">
- }}}
- 
- == Performance Tuning ==
- 
- DougChestnut recommends to adapt the garbage collector to make use of all 
available CPU cores. This can be done by adding the following to your JAVA 
options (for a machine with 4 cores):
- {{{
- -XX:+UseParallelGC -XX:ParallelGCThreads=4 
- }}}
- You can also increase stack and heap size to make better use of available 
memory (be careful not to starve other processes on the same machine, though):
- {{{
- -Xms512m -Xmx1024m 
- }}}
- 
- see also HowToPerformance.
- 
- for Tomcat performance hints see 
http://marc.theaimsgroup.com/?t=103598885300001&r=1&w=2
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to