FAQ

繁 | 簡 | GET A TRIAL | PURCHASE
   


FAQ Home 

Curtain e-locker
Installation Guide
User Guide 

Curtain LogTrace 

Curtain MonGuard

Website Product Page
Curtain e-locker
Curtain LogTrace
Curtain MonGuard 
 
FAQ No.:00368 
Category:Sales & Marketing 
 
Question:

Recommendations for Configuration and Optimization for a Large Number of Clients

 
 
Answer:The performance of Curtain e-locker can be impacted by several factors. The number of Client PCs plays a role, as each one periodically checks its permissions with the Curtain Admin Server and uploads activity logs. Using LDAP to retrieve a huge number of users and user groups can increase the pressure on e-locker to check permissions. Additionally, having a large number of e-locker Policy Groups increases the transmission demand between Client and Server, especially when there are many users, affecting both performance and bandwidth. It's important to configure and optimize your system to ensure optimal performance. Here are some key recommendations:
    • Higher Hardware Specifications:
      • Use higher specifications for hardware, such as more CPU cores and increased RAM. This will help handle the higher load and ensure smooth performance.

    • Adjust Communication Frequency:
      • Adjust the frequency of communication between clients and the Curtain Admin Server based on usage needs. For example, if policy permissions are not frequently changed, you can set the check to every 60 minutes or once a day.

    • Limit User Groups in LDAP:
      • Include only the necessary users and user groups in LDAP to reduce the pressure on e-locker when checking permissions.

    • Avoid Duplicate Policies:
      • Remove duplicate or unused policies to reduce the transmission demand between Client and Server.

    • Monitor and Optimize Bandwidth Usage:
      • For clients using dedicated lines, MPLS or cloud based services, monitor and optimize bandwidth usage by adjusting sync times and log upload frequencies.

Here are some scenarios for reference.

Scenario 1: MonGuard client using screen watermark
    • Client Count: 2600
    • Curtain Admin on Cloud, using a dedicated line, wishing to reduce bandwidth.
    • Requirements: 85% response success rate

    Recommended Hardware

    CPU : 8/16 Cores

    Ram : 16GB RAM

    More CPU cores can handle more Client Requests simultaneously. For dedicated line requirements, set sync time to once a day and no log uploads.

    • Max Concurrent Client Requests: 12/24
    • Max Concurrent Download Requests: 6/12
    • Request Report Status, Report status and Query Setting: 1440 minutes
    • Upload Log, Upload Print log: Unchecked

    e-locker data loss prevention (DLP) - using screen watermark
Scenario 2: LogTrace client using Log functionality
    • Client Count: 600
    • 2 Sites through VPN
    • Requirements: 90% response success rate

    Recommended Hardware

    CPU : 4 Cores

    RAM : 8GB

    Given their smaller number of clients, even with different sites, default durations for sync policy and log uploads are sufficient.

    • Max Concurrent Client Requests: 10
    • Max Concurrent Download Requests: 5
    • Request Report Status, Report status and Query Setting: 10 minutes
    • Upload Log, Upload Print log: 15 minutes

    e-locker data loss prevention (DLP) - using Log functionality

Scenario 3: e-locker client using full features
    • Client Count: 1500
    • Internal Network
    • Requirements: 95% response success rate

    Recommended Hardware

    CPU : 8 Cores

    RAM : 8/16GB

    With a stable network, an 8-Core CPU can handle Client Requests simultaneously.

    • Max Concurrent Client Requests: 12
    • Max Concurrent Download Requests: 6
    • Request Report Status, Report status and Query Setting: 10-30 minutes
    • Upload Log, Upload Print log: 15-30 minutes

    e-locker data loss prevention (DLP) - using full features

For Curtain e-locker usage examples, please refer to FAQ 00322 - Usage case of Curtain e-locker