In jadice web toolkit for displaying documents, the backend renders Tiles as images that can be displayed in the Browser. The details are described in the documentation. 

This page is intended to give an overview of the different options for generating the Tiles when it comes to file-size, memory consumption and response time.

Overview

Details

Test setup

• JMeter 5.3
  • 20 Threads
  • Ramp-up 15s
  • 50 loops
• Tomcat 9.0.40
• Java
  openjdk version "11.0.9.1" 2020-11-04
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.9.1+1)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.9.1+1, mixed mode)
• jadice web toolkit 5.10.6.1
• Docker Image: tomcat:9.0.40-jdk11-adoptopenjdk-hotspot
• Docker command:
  docker run -p 8080:8080 -p 9010:9010 -m 3072m --cpus=4 jwt-tomcat11
  • 9010 used for JMX monitoring
• Jadice.properties:
  jadice.viewer.cache.sizeHighwaterMarkPercent=25
jadice.viewer.cache.maxNumberOfCacheEntries=3000
jadice.viewer.cache.maximumExpiryObjectCountRatio=10
jadice.viewer.cache.maxAgeExpiryEnabled=true
jadice.viewer.cache.maxAge=30
jadice.viewer.cache.maxAge.timeUnit=MINUTES
• Tile-Caching disabled

Test 1

Scenario

These results were performed on the same machine so the response time can be considered as "render time" since the transfer doesn't traverse over an actual network

Test result

Test 2

Scenario

The application was accessed via the internet with the following connection types:

• Client (JMeter): Fibrechannel 1GBit/s download 1GBit/s upload
• Host: Coax 1GBit/s download 50MBit/s upload
• average ping to host: 32ms
• hops to host: 11

Test result