Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
I was tuning my informix with the onconfig and env
variables, when I saw the output of onstat -g ses <sesid> with something like
this:
tid name rstcb flags curstk status
78 sqlexec b154a5b4 ---P--- 67400 b154a5b4 sleeping(secs: 3)
112 scan_1.0 b1553554 ------- 68296 b1553554 running
114 scan_2.0 b155414c Y------ 68296 b155414c cond wait(await_MC2)
118 scan_3.0 b1554d44 Y------ 68296 b1554d44 cond wait(await_MC3)
It used to have only the sqlexec thread on the output before I changed the
parameters. Can anybody tell me what are those scan_1.0, scan_2.0, and
scan_3.0? Does it help in the performance?
It means that you are doing parallel scans.
"EDMUND LAJARA"
<edmund.lajara@no To: ids@iiug.org
kia.com> cc:
Sent by: Subject: new scan threads [827]
forum.subscriber@
iiug.org
03/31/2003 01:55
PM
I was tuning my informix with the onconfig and env variables, when I saw
the output of onstat -g ses <sesid> with something like this:
tid name rstcb flags curstk status
78 sqlexec b154a5b4 ---P--- 67400 b154a5b4 sleeping(secs: 3)
112 scan_1.0 b1553554 ------- 68296 b1553554 running
114 scan_2.0 b155414c Y------ 68296 b155414c cond wait(await_MC2)
118 scan_3.0 b1554d44 Y------ 68296 b1554d44 cond wait(await_MC3)
It used to have only the sqlexec thread on the output before I changed the
parameters. Can anybody tell me what are those scan_1.0, scan_2.0, and
scan_3.0? Does it help in the performance?
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.