Hunk®(Legacy)

Hunk User Manual

Download manual as PDF

Download topic as PDF

About data model acceleration

Data model acceleration lets you create data models for data that includes virtual indexes. Hunk Data Model Acceleration uses cached information that can map extremely large datasets to accelerate searches.

Data model information that is stored in Splunk Enterprise indexes uses tsdix files. Hunk data models access data for virtual indexes that points to data in Hadoop, so you can create data models on any file types that a Hunk virtual index can point to. Hunk stores the store the data model acceleration files in Parquet and ORC.

For more information about how Data Model Acceleration works in Splunk Entperprise, see Accelerate data manuals in the Splunk Enterprise documentation.

How data model acceleration works in Hunk

1. You create a new data model Configure data model acceleration

2. Hunk creates a data model acceleration summary file for each raw data file:

  • Hunk maintains information about the data model acceleration summary files in the KV Store (this allows Hunk to perform a quick lookup).
  • Hunk stores the actual data model acceleration summary files in Hadoop.

3. In the case of a data model that covers a large time range, such as "one year" or "all time". You can partition data model files into buckets the same way you would in Hunk Report Acceleration.. This makes both updating lookup files at model creation time and loading lookup files at search time faster. For more information see Hunk Report Acceleration.

4. You can run a search on data in Hunk virtual indexes that can also include Splunk Enterprise indexes. If a data model exists for any Splunk Enterprise data, data model acceleration will be applied as described In Accelerate data models in the Splunk Knowledge Manager Manual.

5. For tstats/pivot searches on data models that are based off of Virtual Indexes, Hunk uses the KV Store to verify if an acceleration summary file exists for a raw data split.

6. If an acceleration summary file is not found for the raw data split, Hunk falls back to the original data file and does a regular search of the virtual index.

7. If an acceleration summary file is found, then the summary file is used instead of the raw data file.

8. The existing saved summary data is used to return data faster for a search that is comprised of all or part of that data model.

PREVIOUS
Manage report acceleration
  NEXT
Configure data model acceleration

This documentation applies to the following versions of Hunk®(Legacy): 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters