https://community.splunk.com/t5/Splunk-Enterprise/Slow-Search-Performance/m-p/694217#M19832 <P>Hi,</P><P>we moved a customer from virtualized splunk indexers to physical machines with nvme storages. Since me performed this migration the customer experiences slower results when running dense searches. So i checked the job inspector and it seems, that there is an issue . As far as i understood the value "dispatch.fetch" is the time the SH waits for the idx to return the results. Is this value based on network or storage conditions?</P><P>Attached the slightly blurred job inspector</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="spl_problem.png" style="width: 648px;"><img src="https://community.splunk.com/t5/image/serverpage/image-id/31880i78BCEB912470C209/image-size/large?v=v2&amp;px=999" role="button" title="spl_problem.png" alt="spl_problem.png" /></span></P> Wed, 24 Jul 2024 14:39:09 GMT DanielAmlung 2024-07-24T14:39:09Z https://community.splunk.com/t5/Splunk-Enterprise/Slow-Search-Performance/m-p/694217#M19832 <P>Hi,</P><P>we moved a customer from virtualized splunk indexers to physical machines with nvme storages. Since me performed this migration the customer experiences slower results when running dense searches. So i checked the job inspector and it seems, that there is an issue . As far as i understood the value "dispatch.fetch" is the time the SH waits for the idx to return the results. Is this value based on network or storage conditions?</P><P>Attached the slightly blurred job inspector</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="spl_problem.png" style="width: 648px;"><img src="https://community.splunk.com/t5/image/serverpage/image-id/31880i78BCEB912470C209/image-size/large?v=v2&amp;px=999" role="button" title="spl_problem.png" alt="spl_problem.png" /></span></P> Wed, 24 Jul 2024 14:39:09 GMT https://community.splunk.com/t5/Splunk-Enterprise/Slow-Search-Performance/m-p/694217#M19832 DanielAmlung 2024-07-24T14:39:09Z