Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 309 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Batch job/job ques takes different time in BC
christophersvensson
Member Posts: 6
Hi,
We are at a performance testing stage with a customer. We have an isolated on prem environment (BC22). We are testing batch jobs. We are running identical tests with the same amount of data, and the same code. But the time the jobs takes, differs from 2 hours to 6 hours.
BC runs on a Azure platform with and Business Critical SQL database with 4vCores and read scale out enabled.
Have anyone here experienced similar issues? That Batch jobs/job ques varies this much in time? Never seen it before.
We are at a performance testing stage with a customer. We have an isolated on prem environment (BC22). We are testing batch jobs. We are running identical tests with the same amount of data, and the same code. But the time the jobs takes, differs from 2 hours to 6 hours.
BC runs on a Azure platform with and Business Critical SQL database with 4vCores and read scale out enabled.
Have anyone here experienced similar issues? That Batch jobs/job ques varies this much in time? Never seen it before.
0
Answers