Is debug enabled for my searches, and can this affect my search performance?

[a212830]

Hi,

I was looking at the job inspector on one of my SH's and noticed that debug is enabled within the job inspector. Is this normal? Would this slow down the search?

DEBUG: [zdal134] search context: user="a212830", app="search", bs-pathname="/apps/splunk/var/run/searchpeers/A7306951-22E1-4738-80A4-96B078998846-1412380262"
DEBUG: [xdal138] search context: user="a212830", app="search", bs-pathname="/apps/splunk/var/run/searchpeers/A7306951-22E1-4738-80A4-96B078998846-1412380262"
DEBUG: [1dal139] search context: user="a212830", app="search", bs-pathname="/apps/splunk/var/run/searchpeers/A7306951-22E1-4738-80A4-96B078998846-1412380262"
DEBUG: [6mmk254] search context: user="a212830", app="search", bs-pathname="/apps/splunk/var/run/searchpeers/A7306951-22E1-4738-80A4-96B078998846-1412380262"
DEBUG: [pmmk255] search context: user="a212830", app="search", bs-pathname="/apps/splunk/var/run/searchpeers/A7306951-22E1-4738-80A4-96B078998846-1412380262"

[jrodman]

Debug level for search processes should normally be controlled via $SPLUNK_HOME/etc/log-searchprocess-local.cfg, however people often modify $SPLUNK_HOME/etc/log-searchprocess.cfg. The -local file is an override file and may not exist.

It's also possible I'm misinterpreting because there isn't a lot of context here.

DEBUG messages can affect search speed when they are extremely frequent, to the point that the search process spends far too much time writing to the logs and not enough time doing search work. A look at the dispatch directory of the search in question to evaluate the size of the search.log files would quickly clarify if that is likely.