Speed up your XPages Application performance

© Maarga Systems Inc., 2012© Maarga Systems Inc., 2012
Maarga Systems

© Maarga Systems Inc., 2012
Lakshmi Sankaran
Project Lead
Maarga Systems
http://bit.ly/9mobile

 Introduction
 Factors affecting performance
 Best Practices – Server Level & Application
Level
 Common Bottlenecks & fixes
 Tools to identify common bottle-necks
 Q&A

 Application Modernization – XPages App
Deployment/Maintenance is critical
 Server-Level & Application-Level parameters
to be properly configured.
 Performance a constraint for adoption, if not
addressed properly

 Server Capacity
 User Community and concurrent user load
 Network Speed / Bandwidth
 Application Heaviness – GBs
 Last but not the least – Code Quality.

 Recommended H/W & S/W configurations of
Server
 notes.ini configuration
 Xsp properties

 OS – A 64 bit OS is recommended
 32-bit Domino has limits on setting
HTTPJvmMaxHeapSize (<= 512 MB)
 Memory - Give Server lots of RAM
 More the RAM, more can be the
HTTPJvmHeapSize
 Isolate heavily used XPages Apps from other
memory intensive apps such asTraveller

 HttpJVM MaxHeapSize
 Set to 1/4th of available RAM
 HttpJavaMaxheapSizeSet
 Set to 1 to prevent MaxHeapSize from reverting
to default value.
 Default is 256M for 851 servers, 64M for 852
Servers

 Use run-time optimized java script
 Configure Server Page persistence to keep
pages in memory (small no. of users) and disk
(for large users)
 Configure appropriate application/session
time-out to prevent inactivity
http://books.google.co.in/books?id=PWmRO0qrjKUC&pg=PT29&lpg=PT29&dq=sample+xsp+
properties+file&source=bl&ots=M2yUrpIeqF&sig=AcSp4SrcUJEMEluZO_8dDGPtRZk&hl=
en&sa=X&ei=dseuUeXQGciVrgfw_oHwBw&ved=0CGgQ6AEwCA

 xsp.persistence.mode = fileex
 Xsp.persistence.maxviews = 16
● Server-side control tree caching. Also the related options:
● xsp.persistence.file.maxviews, xsp.persistence.file.gzip, xsp.persistence.file.threshold,
xsp.persistence.dir.xspstate
 xsp.application.timeout=30min
 xsp.session.timeout=30min
● Server timeouts
 ibm.jscript.cachesize
● Server-side JavaScript expression cache
 xsp.compress.mode=gzip
● Network files are smaller (enabled by default)
 xsp.resources.aggregate = true
● Fewer requests for CSS and JS files, aggregated files are cached
 xsp.expires.global=10days
● Browser expiration for CSS & JS global files [global == not in application]

 Out of Memory Exceptions
 Check HttpJVMMaxHeapSize
 SessionTime-Outs
 Check time-out interval
 Higher Load times
 Application Size - Check Views, Index Sizes
 Lookups
 Partial Refreshes
 Scoped variables – Application / Request Scopes

 Which of the following tools you have used
during your development process
 XPages tool box
 YSlow
 Pagespeed
 Extended Status Bar
 FireBug

 XPagesTool Box
 Yslow/Page Speed
 Firefox Extended Status Bar

 Usage of XPagesTool Box
 CPU / Memory / Backend Profiling can be done
 Backend Profiling –Wealth of information on
methods and their usage
 Should be used during development/Testing
cycles
 Production use – Only for critical problem
resolution

 IncreasingView Index Sizes
 Recreate views – DO NOT copy/paste existing
Views.They tend to increase sizes
 Avoid Duplicate aliases –View indexes get
doubled.
 Golden Rules
 Remove unnecessary Sorting/Styling of columns
 Avoid Complex formulas inViews
 Avoid @Now or @Today inViews

 Free-up memory
 Purge Indexes
 Compact Db (Copy Style option) and Re-Build
Indexes

 Optimize usage of DB Lookups/Columns –
They are highly expensive
 XpagesTool Box comes in Handy – Identify
no. of dblookup calls and their places
 Use caching of dblookup results

 Commonly used in fields.
 Check options – Do notValidate or Update
data, Process data withoutValidations, Set
Partial Execution mode
 Disallow user action during Partial Refresh
 Using static ‘Loading’ indicator

 Optimized usage of Scoped variables
 Application Scope
 Application level variables that is common to all
users can be stored (e.g) – Path of a Lookup DB,
Server etc..
 Request Scope
 Query String related parameters

 View Scope
 Session Scope
 User level information
 Employee details – As long as the employee
session is active, the information is available to
access

 Memory leaks are possible when objects are
not recycled properly.
 Use Recycle() to remove all Domino objects
after use.
var aView:NotesView = database.getView("SomeViewName");
var doc:NotesDocument = aView.getFirstDocument();
while (doc) { // do some processing on doc
doc = aView.getNextDocument( doc );}
--------------------------------- (to) -----------------------------------------------------------------------
var vw:NotesView = db.getView("SomeViewName");
var doc:NotesDocument = vw.getFirstDocument();
while (doc) { // do some processing on doc
var nextdoc:NotesDocument = vw.getNextDocument( doc );
doc.recycle();
var doc:NotesDocument = nextdoc; }

 Need for performance Optimization
 Server – Level Parameters
 Xsp properties
 Application Level changes – Coding Best
Practices

 http://www.entwicklercamp.de/konferenz/ent2013.
nsf/bc36cf8d512621e0c1256f870073e627/815cc2ed1
4d57f39c1257a44002b8b22/$FILE/T4S6-
Performance.pdf
 http://bruceelgort.files.wordpress.com/2012/05/ad
mindev2012_elgort_experttipsandtricks1.pdf
 http://xpageswiki.com/web/youatnotes/wiki-
xpages.nsf/dx/Memory_Usage_and_Performance

ThankYou

Speed up your XPages Application performance

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (11)

Similaire à Speed up your XPages Application performance

Similaire à Speed up your XPages Application performance (20)

Plus de Maarga Systems

Plus de Maarga Systems (11)

Dernier

Dernier (20)

Speed up your XPages Application performance

Notes de l'éditeur