At the very least it will provide some marginal improvement. If there is
indexing though, that is a synchronous task and that can also use
significant CPU and I/O.

Both need to be addressed.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve
Sent: Thursday, May 22, 2014 9:15 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Running jobs on a separate core

Brian wrote:
In reviewing various documents a lot of them point to
creating a new subsystem and pushing the QZDASOINIT jobs onto
I guess it's something we'll have to investigate once the new box arrives.


Isolating the QZDASONIT jobs to an "ODBC" subsystem with its own memory pool
is probably going to fix your problem.

Here are the instructions provided by Bryan Dietz for isolating QZDASOINIT


This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page