middle manager configuration for runtime.properties in micro-quickstart env

druid.service=druid/middleManager
druid.plaintextPort=8091

# Number of tasks per middleManager
druid.worker.capacity=4
druid.worker.baseTaskDirs=[\"var/druid/task\"]

# Task launch parameters
druid.indexer.runner.javaOptsArray=["-server","-Xms1g","-Xmx1g","-XX:MaxDirectMemorySize=1g","-Duser.timezone=UTC","-Dfile.encoding=UTF-8","-XX:+ExitOnOutOfMemoryError","-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager"]

# HTTP server threads
druid.server.http.numThreads=12

# Processing threads and buffers on Peons
druid.indexer.fork.property.druid.processing.numMergeBuffers=2
druid.indexer.fork.property.druid.processing.buffer.sizeBytes=100MiB
druid.indexer.fork.property.druid.processing.numThreads=1

# Hadoop indexing
druid.indexer.task.hadoopWorkingPath=var/druid/hadoop-tmp

How are you ingesting the dataset? Where does the majority of the time go? If creating such a small dataset takes abnormally more time, I’d look at the setup to make sure that there aren’t any bottlenecks