SearchBlox Developer Documentation

Welcome to the SearchBlox developer documentation. Here you will find comprehensive technical documentation to help you start working with SearchBlox as quickly as possible, as well as support if you get stuck. Let's jump right in!


Installation Tuning

To tune the application for high performance, please allocate the recommended amount of CPU and memory based on your documents, number of collections and number of search users.

1.) Start by verifying the amount of memory utilized by SearchBlox and Elasticsearch

Verify Memory Allocation

  • You can verify the memory allocated to SearchBlox in the Admin Dashboard license page

Verify Elasticsearch Memory Allocation

Improve Concurrent Collections Indexing

  • If you plan to run multiple collections simultaneously you can increase performance by increasing the jetty thread values in <SEARCHBLOX_INSTALLATION_PATH>/start.ini
  • By default, minThreadPool count is 20 and max ThreadPool count is 100. We recommend increasing the thread pool count as shown below for multiple collections with larger datasets.
  • Update start.ini with the following snippet at the end of the file and restart the SearchBlox service.
# --------------------------------------- 
# Module: threadpool
# Enables the Server thread pool.
# --------------------------------------- 

### Server Thread Pool Configuration
## Minimum Number of Threads

## Maximum Number of Threads

## Number of reserved threads (-1 for heuristic)
# jetty.threadPool.reservedThreads=-1

## Thread Idle Timeout (in milliseconds)

## Whether to Output a Detailed Dump

Updated about a month ago

What's Next

You can go through the related sections below


Installation Tuning

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.