| Subject: | Replication Processing Finetuning and Performance Improvements |
| Summary: | We need to review Replication Processing Finetuning and Performance Improvements for customers that are: - Processing very high volumes of transactions
- Allow customers to perform transactions on the Replication server
|
| Audit Notes: | Edited by sanjay on 07/08/23 16:11. Edited by sanjay on 07/08/23 16:11. Edited by sanjay on 07/08/23 15:33. |
| 27 Jul 2023 | 09:20AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 02-08-2023 01:14 PM Time Taken: 46.00 Notes: ETC extended from: 27/07/2023 to 02/08/2023 |
| PART A - Development work for this case has been completed. 1. The change will be available in versions: 15.00 and 14.90.230727 2. The following changes were made(Include Database object names, Program classes, and any other relevant information): - Changed the "In" and "OUT" "Queue Processing" to process a maximum of 5 sets of 1000 rows at a time.
- Previously, the "IN" and "OUT" Queue Processing was processing ALL "Queue Data" in a single step in batches of 1000. This causes an issue when the initial Upgrade pushes a very high volume of data through the Queues, or when a customer is uploading large volumes, including bulk price changes and Bulk Inventory Updates.
- Added NO Locks to Queue Processing
- Added control to prevent "IN QUEUE" to process at the same time as "OUT Queue" to avoid record locks
3. Affected Areas: - Replication Data Processing
4. The issue was caused by: - Improvement
5. Other Relevant Notes:
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
| 27 Jul 2023 | 11:50AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 02-08-2023 03:42 PM Time Taken: 6.00 |
| When recomputing Customer Balance, we exclude POSCASH. Added a Parameter in Customer Balance Recompute where "Credit Limit" is "Greater than". The default value is Zero. Therefore, "Credit Limit = 0" customers will not have their balance recomputed. |
|
| 03 Aug 2023 | 11:25AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 09-08-2023 03:22 PM Time Taken: 5.00 Notes: ETC extended from: 02/08/2023 to 09/08/2023 |
| When adding Location Filters to Replication servers, we do not allow a location to be used in multiple servers. We have removed this limitation so the HQ server will filter transactions. This is useful for OTGL FLEETPLUS, which wants to receive transactions from all locations. We, therefore, add All locations to the Fleet Plus server configuration. |
|
| 07 Aug 2023 | 03:33PM Comment 4 by Sanjay (Link Technologies) Case L12930 added to project 14.90 |
| 08 Aug 2023 | 10:59AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 10-08-2023 02:57 PM Time Taken: 11.00 Notes: ETC extended from: 09/08/2023 to 10/08/2023 |
|
The following tests were performed:
Table 1 - Test Results
| No | Test Case | Expected Result | Pass/Fail | Comments | | 1 | Verify that the Location Filter sends data to selected locations only
|
| Pass
|
| | 2 | When there are no location Filters, all data goes to the configured server
|
| Pass
|
| | 3 | Can share locations amongst configured locations
|
| Pass
|
|
Environment Details - OS version: Win11
- Application version: 14.90.230810
- Setup on:
- Server: LinkQA4
- Database: LinkSOFT
- LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
- Login Details: Standard username and password for user "admin"
Next Step: Closure
|
|