-
-
Save jgstew/51a99ab4b5997efa0318 to your computer and use it in GitHub Desktop.
__RelaySelect_Automatic=1 | |
_BESClient_Resource_StartupNormalSpeed=1 | |
_BESClient_Download_RetryMinutes=1 | |
_BESClient_Download_CheckAvailabilitySeconds=120 | |
_BESClient_Resource_WorkIdle=20 | |
_BESClient_Resource_SleepIdle=500 | |
_BESClient_PowerHistory_EnablePowerHistory=1 | |
_BESClient_Comm_WakeOnLanForwardingEnable=1 | |
_BESClient_Comm_CommandPollEnable=1 | |
_BESClient_Comm_CommandPollIntervalSeconds=7200 | |
_BESClient_Comm_EnableConnectionTriggers=1 | |
_BESClient_Log_Days=30 | |
_BESClient_Log_MaxSize=1536000 | |
_BESClient_Report_MinimumInterval=60 | |
_BESClient_Report_Encryption=optional | |
_BESClient_Download_MinimumDiskFreeMB=2000 | |
_BESClient_Download_UtilitiesCacheLimitMB=500 | |
_BESClient_Download_DownloadsCacheLimitMB=5000 | |
_BESClient_Download_NormalStageDiskLimitMB=500 | |
_BESClient_Download_PreCacheStageDiskLimitMB=1000 | |
_BESClient_Query_WorkTime=250 | |
_BESClient_Query_SleepTime=500 | |
_BESClient_Query_NMOMaxQueryTime=30 | |
_BESClient_Resource_AccelerateForPendingMessage=1 | |
_BESClient_ActionManager_HistoryKeepDays=1825 | |
_BESClient_ActionManager_HistoryDisplayDaysTech=90 | |
_BESClient_ActionManager_UIActionRunningTopmost=1 | |
_BESClient_Download_DirectOnFail=1 | |
_BESClient_ActionManager_CompletionDialogTimeoutSeconds=30 | |
_BESClient_Inspector_ActiveDirectory_Cache_MaxUsers=10 | |
_BESClient_Inspector_ActiveDirectory_UserRefresh_Seconds=129600 |
@Sujaygr those 2 settings are unrelated. _BESClient_Query_SleepTime
and _BESClient_Query_WorkTime
are used to determine how much effective CPU usage the client will use when it gets a "FastQuery" relevance evaluation request. These are very rare and meant to be completed quickly, so I set the CPU usage much higher than the default. These evals time out after 60 seconds if they don't complete fast enough, and this is never used unless you actually send a client a FastQuery.
_BESClient_Resource_AccelerateForPendingMessage=1
should tell the client that if it is not in the idle state, like it is processing an action, then it shouldn't switch back into the idle state until it deals with the incoming message. This would cause the Client that is actively doing work to stay a bit more active a bit longer than normal. This can be a big help when trying to speed up initial client provisioning.
It is very possible to have more aggressive settings for the defaults using the clientsettings.cfg
file and then tune them to be lower after the client has been installed for a period of time: (example: 3 days)
Hi Stew, I have a quick question here. Can you please shed some light on below 2 settings, I think they are conflicting with each other?
_BESClient_Resource_AccelerateForPendingMessage=1
_BESClient_Query_SleepTime=500