Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One of the main reasons is that you have a large application with many modules, classes, manifests, XML descriptors so on, and the fact that Websphere application server start up process is single threaded per se (thus each application may be started in a separate thread if they has equal weight). One other reason is that the Eclipse EMF and JST frameworks are very I/O intensive during startup and publish/deploy. </p> <p>One other reason for the tedious start up is the annotation scanning which will occur during publish/deploy. This annotation scanning can be controlled and modified in a various ways. Look at this site: <a href="http://wasdynacache.blogspot.se/2012/05/how-to-speed-up-annotation-processing.html" rel="nofollow">http://wasdynacache.blogspot.se/2012/05/how-to-speed-up-annotation-processing.html</a></p> <p>First of all, examine and evaluate your hardware, both CPU, memory and HDD. Is your processor/s running 100% for a long time during start up? If so, the processor may be too weak. Is paging occur? then you may have to put in some more RAM. The Websphere/eclipse JST and EMF frameworks are very I/O intense so you should consider to invest in a SSD disc. You should also make sure that other processes on your machine (virus protection software etc.) don´t steal hardware resources from the Websphere java processes. </p> <p>So for the hardware: 1. Processor - a pretty fast one, since the publish and the startup is mostly singlethreaded you do not need that many cpu cores 2. Memory - You will at least need 512Mb of physical RAM, this depends of the size of your application of course. 3. Storage - I would definitely go for a fast SSD since the underlying eclipse framework is I/O intensive.</p> <p>Here are some tricks to reduce the footprint of the start up phase. Please before applying these settings make sure that you record a baseline start up so that you can observe the difference in start up, i.e. the reduced start up time.</p> <ol> <li>JVM args : -Xverify:none -Xquickstart -Xnoclassgc -XX:+UseNUMA -XtlhPrefetch -Xgcthreads4 (I got 4 virtual processors installed on my machine) </li> <li>Extend the heap size to match the demands of your application.</li> <li>Disable the autostart of the application to reduce publish time.</li> <li>Disable PMI and unnecessary tracing.</li> <li>Profile your application during startup and fix bottlenecks if found any.</li> </ol> <p>Other JVM arguments that may gain performance:</p> <ul> <li>com.ibm.cacheLocalHost=true</li> <li>com.ibm.ws.classloader.zipFileCacheSize=512</li> <li>com.ibm.ws.classloader.resourceRequestCacheSize=1024  </li> <li>com.ibm.ws.management.event.pull_notification_timeout =20000</li> <li>com.ibm.ws.amm.scan.context.filter.packages=true</li> <li>org.eclipse.jst.j2ee.commonarchivecore.disableZip=true</li> </ul> <p>Jvm arguments that will make the Websphere application server to stop immediately:</p> <ul> <li>com.ibm.ejs.sm.server.quiesceTimeout=0</li> <li>com.ibm.ejs.sm.server.quiesceInactiveRequestTime=1000</li> </ul> <p>Webcontainer properties:</p> <ul> <li>com.ibm.wsspi.jsp.disableTldSearch=true</li> <li>com.ibm.wsspi.jsp.disableResourceInjection=true</li> </ul> <p>JVM arguments that may be specified eclipse.ini (Note that the heap parameters is configured according to the conditions of my environment)</p> <ul> <li>-Dcom.ibm.ws.management.event.max_polling_interval=5000</li> <li>-Xquickstart</li> <li>-Xverify:none</li> <li>-Xmxcl25000</li> <li>-Xjit:dataTotal=65536</li> <li>-Xcodecache64m</li> <li>-Xscmx48m</li> <li>-Xnolinenumbers</li> <li>-Xverify:none</li> <li>-Xmnx64m</li> <li>-Xmx1446m</li> <li>-Xmnx64m</li> <li>-XX:+UseCompressedOops</li> <li>-XX:+UseNUMA </li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWebsphere Application Server - What on earth will it take to start any fast?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRobert Höglund
    1. USRobert Höglund
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload