×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
Landess
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
it<<<<<.
I guess it's something we'll have to investigate once the new box arrives.
Brian:
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
jobs:
http://wiki.midrange.com/index.php/QZDASOINIT
-sjl
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
