The Cryptshare Server becomes unresponsive under high load.

The Cryptshare Server becomes unresponsive under high load.

Applies to:

All versions of Cryptshare Server

Symptom:

The Cryptshare Server responds slowly when it is used by a large amount of users at a time.


Cause:

The Cryptshare Server tries to respond to all requests but cannot answer the requests faster than they arrive.


Solution:

Solution 1: Increase the Amount of Available Resources

The slowdown can be caused by the Cryptshare Server not having access to enough resources to process all requests. Increasing the available RAM or using a faster CPU can solve this.

Solution 2: Adjust the Web Server Configuration

The configuration file "resources/WEB-INF/ui-config.xml" in the Cryptshare Server installation directory can be used to adjust how the web server behaves, the following section includes comments to highlight the options that can be adjusted to improve performance under high load. You can find the full documentation for the configuration file in the Jetty Wiki.

ui-config.xml  Expand source

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "resources/WEB-INF/configure.dtd">
<Configure id="Cryptshare" class="org.eclipse.jetty.server.Server">
<Arg name="threadpool">
<New class="org.eclipse.jetty.util.thread.QueuedThreadPool">
<Arg name="minThreads" type="int">5</Arg>
<Arg name="maxThreads" type="int">25</Arg>
<Arg name="idleTimeout" type="int">1000</Arg>
<Arg name="queue">
<New class="java.util.concurrent.ArrayBlockingQueue">
<Arg type="int">200</Arg>
</New>
</Arg>
</New>
</Arg>
<Call name="addConnector">
<Arg>
<New class="org.eclipse.jetty.server.ServerConnector">
<Set name="idleTimeout">
<Property name="http.timeout" default="15000"/>
</Set>
</New>
</Arg>
</Call>
<Call id="sslConnector" name="addConnector">
<Arg>
<New class="org.eclipse.jetty.server.ServerConnector">
<Set name="idleTimeout">
<Property name="http.timeout" default="15000"/>
</Set>
</New>
</Arg>
</Call>
</Configure>

Additionally, other settings of the Cryptshare Server can be adjusted to improve responsiveness as described here: Advanced Cryptshare Configuration

    • Related Articles

    • Improve performance for systems under high load

      Inhaltsverzeichnis 1 Applies to: 2 Purpose: 3 Solution: 3.1 1. Update Cryptshare Server 3.2 2. Check system hardware 3.3 3. Assign more memory to Cryptshare application 3.4 4. Change Guest OS settings 3.5 5. Adjust the Web Server Configuration ...
    • Setup public key authentication on Cryptshare Server

      Inhaltsverzeichnis 1 Applies to: 2 Purpose: 3 Solution: 3.1 Using PuTTYgen 3.2 Using openSSH Applies to: All versions of Cryptshare Server Purpose: This is a step-by-step guide with two possible ways to set up public key authentication on a ...
    • Freeing Disk Space on a Cryptshare Server

      Applies to: All versions of Cryptshare Server Purpose: The Cryptshare Server has insufficient disk space to operate properly or requires more disk space to store files. Solutions: Remove old Cryptshare Backups (Versions older than 3.12.x) By default, ...
    • Cryptshare service is not starting on Linux server

      Applies to: Cryptshare Server version 4.0.0.0 to 4.1.3.0 Symptom: The Cryptshare Service doesn't start after updating Cryptshare Server from version 4.0.0.0 to 4.1.x.x . Cause: The upgrade process cannot adjust the custom configuration during the ...
    • Migrating Cryptshare

      Applies to: All versions of Cryptshare Server Purpose: This article guides you through a Cryptshare Server migration. Solution: Be sure that your Cryptshare Server is running at least version 4.3.0 before proceeding. If not, please update as ...