Feedback
Did this article resolve your question/issue?

   

Article

Self Service client launched by Windows Task Scheduler runs slower

« Go Back

Information

 
TitleSelf Service client launched by Windows Task Scheduler runs slower
URL NameP169922
Article Number000117410
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: Windows Vista, Windows 7, Windows 2008 R1/R2, Windows 2012
Other: Windows Scheduled Tasks
Question/Problem Description
Self Service client launched by Windows Task Scheduler runs much slower than same job started outside of Task Scheduler

OpenEdge process launched by Windows Task Scheduler, making a client server connection, runs faster than the same process making a shared memory connection launched from Task Scheduler.

PROBKUP takes longer to run as a Scheduled Task than from the command line or the backup script the Scheduled Task runs.
 
Steps to Reproduce
Clarifying Information
Migrated from Windows 2003 to a later Windows OS (Vista, 7, 2008 R1, 2008 R2)

OpenEdge process launched outside of Task Scheduler run at normal priority and run at normally expected speeds.
OpenEdge process launched by Windows Task Scheduler run at lower priority and run for longer time durations.

Process Explorer (from www.sysinternals.com) used to verify priority level of job by right mouse clicking the process,  selecting properties and viewing the Performance TAB.
Error Message
Defect/Enhancement Number
Cause
Changes to the core code of Windows Vista, Windows 7 and Windows 2008 R1 and R2 change the way Task Scheduler operates. Windows 2008 R2 has Task Scheduler 2.0 embedded. In Task Scheduler 2.0, MicroSoft uses "Credentials management using new security services" as a new feature. The Task Scheduler is now programmed to decrease the priority of any jobs run from Task Scheduler to below normal values for I/O, CPU and Memory operations, so any work scheduled to run are given lower priorities than normal.
 
Resolution
To change the priority of a task defined within the Microsoft Task Scheduler 2.0:
  1. Export the task (right mouse click the task and save the task as an XML file)
  2. Edit the export XML and modify the Priority value which is defaulted to 7. Set it to 5 which is the normal value.
  3. Save the edited XML file.
  4. Delete the original task from Task Scheduler.
  5. Import the task into Task Scheduler.
Workaround
Notes
Example timings of the same 10.2B04 PROBKUP on Windows 2008

### Scheduled Task (original) ###
Backed up 1421261 db blocks in 00:41:23

### Interactive Task ###
Backed up 1421261 db blocks in 00:02:56

### Scheduled Task (Priority 5) ###
Backed up 1421261 db blocks in 00:03:45
Last Modified Date5/8/2017 2:49 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.