When you first start Portal 6 up (or Portal 5.1 for that matter), no matter what gear you are running it on, its going to seem slow. If you are doing an install, or planning on doing one, add this to your post-install task list:
wpsconfig action-precompile-jsp
This will precompile all JSPs within Portal. It will also take a LONG time to run (mine ran at 477+ minutes on a single processor, 2GB VM).
Plan on running this before you deploy to your user community.
Yes, I am agree it is very slow and time consuming. Also, you’ll see some compiling errors on your screen (don’t know why… IBM things…).
I was using precompile but I noticed that it was eating up around 250MB of hdd free space each time.
Does anyone know where this space is being consumed?
The compilation should be under the WAS instance. When it compiles, it creates new java .class files representing the JSP. Here’s a post on Developerworks that details it a little bit more:
http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=181773