Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


  1. Look into template invocation and reducing number of templates invoked
  2. Look into size of view tree and number of recursions
  3. Profile building of view for bottlenecks
  4. Optimized VM arguments 
  5. Pre-built views or groups?
  6. Compress Data Before Transfer
    1. take advantage of browsers compression functionality allowing the server to send compressed HTTP data to the client. For regular text content like HTML, CSS and JavaScript, this compression technique can reduce your data transfer with as much as 90%. Although compression and decompression slightly increases the CPU usage on both the client and the web application server, it’s still much faster than to transfer an excessive data volume.
    2. minimize java script text size. In looking at jquery code, i noticed that the code is very compressed. small variable names, no whitespace. I assume this is to minimize the footprint. While it does make the code very difficult to read/debug, it would be interesting to see the effect on performance. Consider production/debug option to "pack/unpack" js code.

      Optimization Results

Test: Book Lookup, 200 records, 6 columns, read-only


Response Time

Page Size

Server Form Size


3.73 S

7.23 MB


Simple table with client render

1.03 S

90 KB


Simple table with direct datatables render

1.03 S

53 KB