Does anyone know where I can find logging pool settings?
I'm staging about 14000 tests and occasionally it's hitting pretty close to 100% of logging pool usage and I don't know how or whether I can adjust the pool size/other settings if even possible?
I'm using MSSQL 08 R2 with latest ODBC drivers, latest service packs.
Any info would be appreciated!
Logging Pool Usage
You cannot adjust size of the pool and I am not sure this would help.
If ODBC connection is too slow, bigger pool will be overflowed as well, just a little bit later and HostMonitor will need to delay tests anyway...
If "occasionally" means "pretty often", I think its better to speed up ODBC connection/SQL server (if possible) or change logging mode for some test items from "full" to "brief".
Regards
Alex
If ODBC connection is too slow, bigger pool will be overflowed as well, just a little bit later and HostMonitor will need to delay tests anyway...
If "occasionally" means "pretty often", I think its better to speed up ODBC connection/SQL server (if possible) or change logging mode for some test items from "full" to "brief".
Regards
Alex
[quote="KS-Soft"]You cannot adjust size of the pool and I am not sure this would help.
If ODBC connection is too slow, bigger pool will be overflowed as well, just a little bit later and HostMonitor will need to delay tests anyway...
If "occasionally" means "pretty often", I think its better to speed up ODBC connection/SQL server (if possible) or change logging mode for some test items from "full" to "brief".
Regards
Alex[/quote]
At present it is only logging changes, and it is ocassionally - not pretty often.
Given that this entire solution is built on a (65GHz of available CPU cycles and 96GB of RAM) virtual platform, would it not be good to allow an increase? From what I have seen in the past it does take a moment before virtual resource allocation is changed to allow for greater throughput on a VM if all of a sudden it's pushed hard - could that not be part of the problem? What I'm saying is that eventually the resource allocation would change but in the few seconds it takes to do that it might hit the buffer hard if we have lots of tests writing changes.
If ODBC connection is too slow, bigger pool will be overflowed as well, just a little bit later and HostMonitor will need to delay tests anyway...
If "occasionally" means "pretty often", I think its better to speed up ODBC connection/SQL server (if possible) or change logging mode for some test items from "full" to "brief".
Regards
Alex[/quote]
At present it is only logging changes, and it is ocassionally - not pretty often.
Given that this entire solution is built on a (65GHz of available CPU cycles and 96GB of RAM) virtual platform, would it not be good to allow an increase? From what I have seen in the past it does take a moment before virtual resource allocation is changed to allow for greater throughput on a VM if all of a sudden it's pushed hard - could that not be part of the problem? What I'm saying is that eventually the resource allocation would change but in the few seconds it takes to do that it might hit the buffer hard if we have lots of tests writing changes.
Thanks for that Alex. We will wait for the next release.KS-Soft wrote:Ok, we can increase size in next version of HostMonitor.
If log pool usage does not float near 100% all the time but just for several seconds, this should not be a problem. HostMonitor should delay test execution a little bit, that's all.
Regards
Alex
Regards,
Vernon