Sorry Jeff, I missed your last post. I'll put something together for you to test with.
The idea of running Homeseer scripts within GA is not a good one because of the incest that can occur. In particular, GA runs in real time and one does not want to let homeseer run at that high of a priority.
What is reasonable is for GA to spawn off another process at a lower priority and from there execute a script.
There is another package in the library that collects cpu and memory utilization. Puts it in a database, and graphs the results using XLGraph. I run it locally under the name Processor Performance. I suspect it was submitted to the library under this or similiar name. It was done in the same timeframe as GA. This will give you the data to look at to better characterize the system. GA parameters should be set so it is clearly looking for abnormal rather than 1 or 2 sigma performance characteristics.
The idea of running Homeseer scripts within GA is not a good one because of the incest that can occur. In particular, GA runs in real time and one does not want to let homeseer run at that high of a priority.
What is reasonable is for GA to spawn off another process at a lower priority and from there execute a script.
There is another package in the library that collects cpu and memory utilization. Puts it in a database, and graphs the results using XLGraph. I run it locally under the name Processor Performance. I suspect it was submitted to the library under this or similiar name. It was done in the same timeframe as GA. This will give you the data to look at to better characterize the system. GA parameters should be set so it is clearly looking for abnormal rather than 1 or 2 sigma performance characteristics.
Comment