Can we have more than one search per core in Hunk?

[ddrillic]

We have Hunk on a machine of four cores only. Is there a way to use more than one search per core on Hunk? If so, how?

[rdagan_splunk · Accepted solution]

Exactly, in some cases (Hunk normal searches - Stream and Report mode) the search will use the core until the MapReduce is done.
In some cases (Hunk Report Acceleration, Schedule Searches, Summary Indexing, Data Model Acceleration) the search will use the core for very little time.

[ddrillic]

Thank you!!!!!

[rdagan_splunk]

A search head's tasks are primarily CPU bound. As more users and more apps are added to a search head, the concurrent search load climbs quickly and hits a limit. The limit represents the aggregate search load across all users and apps to a search head's CPU cores.
Adding search heads to the deployment increases the aggregate CPU resources, increasing the aggregate search concurrency and the number of active users and apps supported in the environment.
As the search head gains more users, the CPU limitations will become apparent, and users will experience slower search result speed.

[ddrillic]

Great - but since searches in Hunk normally run for a long time, do we have the bind between the search and a core? and therefore in our case, being limited to four concurrent searches...