FGBL07
-Interested User-
Posts: 41
Joined: Sep 8, 2011
|
Posted: Sep 23, 2012 08:15 AM
Msg. 1 of 3
I have a problem on my PC with the Windows Searchindex and the IQFeed client.
I had noticed that whenever I run my chart program (Sierracharts) the Windows Searchindex process starts to use an indecent amount of CPU time. In fact it uses more CPU time than Sierracharts.
Just starting the IQFeed diagnostic tool will have this effect, so Sierracharts itself is not involved.
I'm at a loss what setting for the Searchindex I have got to change to stop this.
I'm using Windows 7 Home Premium 64-bit and IQFeed 4.8.1.7.
Any ideas?
Many Thanks.
|
DTN_Jay_Froscheiser
-VP, Product Operations-
Posts: 1746
Joined: May 3, 2004
DTN IQFeed/DTN.IQ/DTN NxCore
|
Posted: Sep 23, 2012 02:40 PM
Msg. 2 of 3
I ran a few tests and wasn't able replicate this. You mention that just starting the diagnostics will cause this. Are you saying it increases the CPU without even running a test symbol in the diagnostics app? Can you tell if this happens only when the markets are open (I am looking at it on Sunday afternoon so that may be why I don't see any issues).
One thing to check is that you don't have IQFeed logging turned on. You can turn this off in the diagnostics app by going to the logging tab. If for some reason Sierra Charts has logging turned on, this would cause the SearchIndex to continually index the file as it builds. I was able to see the search index using 2-3% CPU when I turned IQFeed logging on.
Unless you are having problems, it is best to keep logging turned off as it will impact performance not only within IQFeed, but ancillary software such as the search indexer or virus scanners.
Jay Froscheiser Telvent DTN
|
FGBL07
-Interested User-
Posts: 41
Joined: Sep 8, 2011
|
Posted: Sep 23, 2012 04:03 PM
Msg. 3 of 3
Working on a Sunday afternoon? Great!
"..Are you saying it increases the CPU without even running a test symbol in the diagnostics app? "
No, sorry, I was misleading on this. I had entered a test symbol (XG#) and started the test.
I have set the log level now to "0 - no logging" and a first test shows that the Searchindexer no longer stresses the CPUs.
Final test will be tomorrow during market hours.
Many Thanks and have a nice Sunday.
|