Home >Technology >Life In The FastLane: Full Speed XPages

Life In The FastLane: Full Speed XPages

Date post:16-Nov-2014
View:4,682 times
Download:9 times
Share this document with a friend
Using XPages out of the box lets you build good looking and well performing applications. However, as XPage applications become bigger and more complex, performance can become an issue and, if it comes to scalability and speed optimization, there are a couple of things to take into consideration. Learn how to use partial refresh and partial execution mode and how to monitor its execution using a JSF LifeCycle monitor to avoid multiple re-calculation of controls. We will show tools that can allow you to profile your code, readily available from OpenNTF, along with a demonstration of how to use them to improve the speed of your code. Still writing SSJS and encounter a significant slow down when using Script Libraries? See, how you can improve the speed of your application using JAVA instead of JS, JSON and even @formulas.
  • 1. Life In The Fast Lane Full Speed XPagesMarch , 21. 22. 2013Faculty Club, Leuven, BelgiumUlrich Krause, BCC Unternehmensberatung GmbHMatthew Fyleman, We4IT

2. About: Matthew Fyleman Lotus Notes/Domino Developer since 1993 Senior Developer at We4IT GmbH Recently focused entirely on XPagesdevelopment Working on We4ITs XPages framework Also on Offline capabilities for We4ITs mobileframework 3. About: Ulrich Krause Lotus Notes/Domino Developer since 1993 Senior Software Architect at BCC OpenNTF Contributor OpenNTF Board of Directors IBM Champion 2011/2012/2013 Blog http://www.eknori.de Notes Forum (http://www.atnotes.de) 4. Agenda Performance, what factors affect it? Java vs. JavaScript Looping through Documents, ViewNavigator vs.GetNextDocument Stringbuilder vs. Concat (+) JSF Lifecycle Listener Partial Update / Partial Execute Variable Resolver Tools 5. XPages Request 6. Hardware The hardware used has a significant influence on performance.There are 3 key elements: CPU Main Memory Hard Disk 7. Hardware CPU Cores / Clock / Cache Poor response time Main Memory Limit defined by the operating system Scalability Weak CPU AND Low Memory Poor overall performance Poor response times Server "hangs" 8. Network Latency Time taken for data transmission between multiple computers on a network Bandwidth Rate of transmission of data Greater Bandwidth+ Lower Latency--------------------------------= Better Connection 9. Client & Browser Hardware How many data requests / responses are transmitted How much data is transferred (size) Caching of resources How much CSJS runs Size / complexity of the CSS Complexity of the site structure 10. Limiting factors on performance Browser / HTTP server Network latency distance/time to server. Bandwidth size of files. Browser limits on concurrent downloads;

Popular Tags:

Click here to load reader

Reader Image
Embed Size (px)