View source | View content page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Show collection (0 pages)
Collections help


Projects:EntityAccessChecker Perfomance Improvements/QA



There are some general improvements that be applied for the EntityAccessChecker process (Calculate access permissions). This new improvements help to reduce the time spent in the process of calculate permissions for entities. For this reason, the main goal of the QA-Test Plan of this project is to ensure that the new EntityAccessChecker process reduces as much as can this overall overhead.

Manual Tests

Several manual test have been done in order to cover some special scenarios.The following manual test have been done:

Performance Tests

Performance manual test have been done for four different roles:

The following steps have been done before and after this project for every role:

The following code is used to execute x1000 times EntityAccessChecker.initialize(). This code is placed into

private void printPageDataSheet(HttpServletResponse response, VariablesSecureApp vars)
      throws IOException, ServletException {
    if (log4j.isDebugEnabled())
      log4j.debug("Output: dataSheet");
    long start = System.currentTimeMillis();
    OBContext context = OBContext.getOBContext();
    System.out.println("Time initialization " + (System.currentTimeMillis() - start));
    long total = 0L;
    for (int x = 1; x <= 1000; x++) {
      start = System.currentTimeMillis();
      total += System.currentTimeMillis() - start;
      if (x % 100 == 0) {
        System.out.println("Execution number " + x + " and average is [" + total + "/" + x + "]="
            + total / x);
    try {

Overhead reduction

The results of this tests can be found here. Besides several snapshots of Yourkit have been captured: One of them is done before changes applied in this project and the other one is done with changes of this project. Download snapshots here.

This test should be applied in a high volume enviroment. This test let us to understand which is the expected reduction in a real customer with high volume enviroment: NOT Done.

Code review

Retrieved from ""

This page has been accessed 120 times. This page was last modified on 6 April 2017, at 14:08. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.