You can run IQJam in your company on your Domino server. Learn how...
Username: Password:
Reset Password | Register
 
Home | Leader Board | Tags | Help
Back to view...
Is there a way to speed up loading / compiling of XPages? 
I have a rather large database that I'm slowing starting to add some small pieces using XPages.
 
It seems like the first time in the XPage piece of the app - each page seems to take forever to load the first time.  Possibly up to 4 minutes...  Then subsequent hits on the page are much much quicker.
 
I assume that the Java stuff underneath is loading into memory or possibly being compiled if I just refreshed the design. 
 
But it also seems that if I don't use the app for a while and have to log in again that there's another delay on most of the pages the first time through and then subsequent hits are again much quicker.  I assume that after lack of use, the server unloads pages from memory.
 
I'm wondering if there's a way to pre-load the pages? Or keep them loaded? I'd hate for the first person in for the day to have a big delay. 
 
I guess I can try changing the performance setting to "Keep Pages in Memory".  Is that typically a smart thing?  Anything else that can be done to eliminate the initial delays? 
 
Thanks 
Domino Development / XPages
Tagged
David Leedy - 4 months ago |  |  | Viewed 128 times

There are 4 Answers

0votes
David,
 
You can modify the application timeouts to keep sessions alive for longer. However it sounds like you have a bigger problem going on. At worst the first load of an XPage should take a couple of seconds longer than usual. So I'd look for the cause of the problem, not trying to workaround it first.
 
Matt 


Matt White - 4 months ago | 
Voting
Vote on the answer to show whether you think the answer is correct or useful to the rest of the community.

Answers with more votes are more visible to the rest of the community


0votes
Hello David,
Have a look at my blog article: http://www.bleedyellow.com/blogs/martin/entry/xpages_and_performance3?lang=nl
It's all about the notes.ini setting JavaMaxHeapSize.
Hope this solves your problem.
 


martin meijer - 4 months ago | 
Voting
Vote on the answer to show whether you think the answer is correct or useful to the rest of the community.

Answers with more votes are more visible to the rest of the community


0votes
Thanks Matt and Martin...
 
Here's the thing...  I guess I just don't know if the server has an issue or if <GASP> it's me..  :)  Here's today's example.  I have a large view.  It's categorized by person name and also by date.  About 10 columns with 5 totaling numbers.  There's maybe 400,000 documents in this view.
 
In the notes client, I can open it and move around and it's pretty quick.  In classic domino web the view doesn't really look that bad and I can move around not too bad.

In Xpages with an Xpage with a view control dropped on and bound it's painfully slow.  Once it finally loads opening a category has more long delays.
 
 I looked for the ini setting HTPJVMMaxHeapSize on my notes.ini file.  This is an iSeries.  I did not see one. Maybe that's the problem?
 
Thanks


David Leedy - 4 months ago | 
Voting
Vote on the answer to show whether you think the answer is correct or useful to the rest of the community.

Answers with more votes are more visible to the rest of the community


0votes
David,
The line with JavaMaxHeapSize is not by default in your notes.ini. You have to add the line. By default the JavaMaxHeapSize is 64MB. In my opinion it's to low. Add the following line in your notes.ini: JavaMaxHeapSize = 128MB (or higher depending on how many memory your server has, I tested this on a server with 1024MB memory). Reboot your dominoserver and test your application again.


martin meijer - 4 months ago | 
Voting
Vote on the answer to show whether you think the answer is correct or useful to the rest of the community.

Answers with more votes are more visible to the rest of the community


 

Latest Answers for Domino Development / XPages