cncjay
Well Known Member
Hey Folks,
I am facing an issue, wanted to get your input.
I recall, there use to be an general rule of thumb: 1 CPU = 1 job queue. With the newest tools releases (in my case 9.1.5.7), does that still hold true ?
I have a batch server VM (8vcpu and 32gb RAM). At random, the jobs take a long time to complete. For example, an EDI job, that will complete in 45mins, will complete in 2+ hours, the next day.
We have looked that the database side of things to ensure no blocking is going on, etc. While there are so many areas I need to delve into, individually one by one so thought to start with the JDE job queues first.
How can you tell if I have reached some sort of a saturation point with the resources? The CPU and/or RAM never max out at 100%. We do run a lot of scheduled jobs overnight.
Any light on this topic will be of great help.
Thanks !!
E1 9.0 update 1 | tools 9.1.5.7
OS 2008R2 x64 | SQL 2008R2 | SP3
I am facing an issue, wanted to get your input.
I recall, there use to be an general rule of thumb: 1 CPU = 1 job queue. With the newest tools releases (in my case 9.1.5.7), does that still hold true ?
I have a batch server VM (8vcpu and 32gb RAM). At random, the jobs take a long time to complete. For example, an EDI job, that will complete in 45mins, will complete in 2+ hours, the next day.
We have looked that the database side of things to ensure no blocking is going on, etc. While there are so many areas I need to delve into, individually one by one so thought to start with the JDE job queues first.
How can you tell if I have reached some sort of a saturation point with the resources? The CPU and/or RAM never max out at 100%. We do run a lot of scheduled jobs overnight.
Any light on this topic will be of great help.
Thanks !!
E1 9.0 update 1 | tools 9.1.5.7
OS 2008R2 x64 | SQL 2008R2 | SP3