Feature #79: conduct trial run on offline batches - Order ID migration - Collaboration Platform for eCosway

Actions

Copy link

Feature #79

closed

conduct trial run on offline batches

Added by chin-yeh over 13 years ago. Updated over 13 years ago.

Status:

Closed

Priority:

Normal

Assignee:

chin-yeh

Category:

offline batches

Target version:

1.0

Start date:

02/08/2011

Due date:

02/11/2011

% Done:

100%

Estimated time:

Resolution:

Fixed

Description

conduct daily trial run for offline batches. It's been scheduled to run from 8-Feb to 11-Feb

schedule to run at 12PM according to the scheduled date(s).
copy the offline data files from the shared folder which located at cwyrnd2-server prior the trial run

History
Notes
Property changes

Actions

Copy link

Updated by chin-yeh over 13 years ago

8-Feb's result:

DailyEV - hang
genMthlyEacctMovement - hang

Actions

Copy link

Updated by chin-yeh over 13 years ago

chin-yeh wrote:

8-Feb's result:

DailyEV - hang

genMthlyEacctMovement - hang

re-run genMthlyEacctMovement and completed without any error.

Actions

Copy link

Updated by chin-yeh over 13 years ago

due to that too many hard-coded emails in the programs, the email sending is disabled from today onward.

Actions

Copy link

Updated by chin-yeh over 13 years ago

chin-yeh wrote:

chin-yeh wrote:

8-Feb's result:

DailyEV - hang

genMthlyEacctMovement - hang

re-run genMthlyEacctMovement and completed without any error.

test result for re-run onDailyEV:

cwyapp1 (app) + cwyapp1(db) = completed in about 4 hours
cwyapp1 (app) + cwydb1(db with order ID converted) = completed in about 11 hours
- the CPU clock speed is slower than cwyapp1 and the loads on cwydb1 is higher than cwyapp1 as well

Based on the test result of the DailyEV, the program will run much faster if point to the cwyapp1 server. The is because of the more powerful CPU and low server load.

Actions

Copy link