• Timing results not unique to a page

    By Howard Greenberg 1 decade ago

    I was checking out the timings on two XPages, both loaded in the browser using the startTimer and stopTimer (works great!)

    I loaded both pages and then reloaded one page.  I then went to the other page and collapsed and expanded the toolbar.  The timing results from the other reloaded XPage got displayed instead of the correct results for the XPage I was looking at.

    I assume the variable storing the results is a scoped variable of some sort?  Is there a way to make this value unique to an XPage so the user will not possibly see the wrong timing results that were really for another page? Given that most folks would be comparing two designs, they might see the wrong results and reach the wrong conclusion.

     

    • Stored in the sessionScope

      By Mark Leusink 1 decade ago

      Howard,

      The timing results are stored in the sessionScope and therefore unique to the current (browser) session/ user. If you want to compare the performance of 2 designs you can assign the timers different id's (e.g. dBar.startTimer("page1"); ) and differentiate between the pages using  that.

      Mark