Skip to content
Performance

Best Practices for Optimizing Performance

Copyleaks is designed for scalability and high performance, handling large workloads efficiently. To get the best results from your integration, follow these best practices to optimize speed, reduce bottlenecks, and maximize efficiency.

Transmitting large amounts of data over the internet slows down performance. Compressing data can reduce payload size by up to 70%, speeding up processing times.

Compress the data before sending it to Copyleaks and add this header:

Content-Encoding: gzip

This is especially useful when submitting large files.

To receive compressed responses from Copyleaks, include this header in your request:

Accept-Encoding: gzip, compress

This ensures faster data transfer between your system and Copyleaks.

Copyleaks offers many configurable features, but enabling unnecessary ones can slow down scans. Only enable what you need.

Some features to disable if not needed:

FeatureDescriptionRecommendation
properties.includeHtmlIncludes results in HTML formatDisable if plain text is enough.
properties.pdf.createGenerates a PDF reportTurn off if you don’t need a PDF.
properties.expirationDefines how long scan data is storedUse 7 days or less for optimal speed.
properties.filtersNarrows search resultsCustomize filters to improve scan efficiency.

Copyleaks runs on cloud infrastructure, dynamically scaling resources based on demand. However, submitting too many requests at once can reduce efficiency.

  • Instead of submitting all documents at once, send them gradually at a controlled rate (N calls per second).
  • If handling large volumes (e.g., 1M+ files), adjust to the maximum allowed rate limit (see Rate Limit Policy).
  • Don’t flood the system with a sudden burst of requests.
  • Instead, start with a low rate and gradually increase to maintain stable performance.

Copyleaks supports different sensitivity levels, balancing speed and comprehensiveness based on your needs.

Set the properties.sensitivityLevel value based on priority:

LevelFocusBest For
1SpeedQuick scans, minimal checks.
3 (default)BalancedMost use cases.
5ComprehensiveDeep analysis, high accuracy.

Each JWT token generated during login is valid for 48 hours.

For more information on obtaining a new token, refer to the Login API.