× 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.



Since you added memory, could there be an issue with a pool being starved?

John McKee

On Wed, Feb 27, 2013 at 9:40 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
Like I mentioned cfint is at essentially zero. No PTFs were loaded
during the hardware work, normal shutdown, and a normal IPL after all
the work was completed.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 2/27/2013 10:36 PM, franz400 wrote:

Just googling v5r1 performance issues - this link is JDE specific

http://www.jdelist.com/ubb/showflat.php?Cat=&Number=48118&page=659&view=collapsed&sb=12&o=&fpart=1

also mention on other posts of the CFINT jobs and the interactive monitor
that existed on the 7xx hardware
(but I would think that would show in the sysact).

Jim Franz

----- Original Message -----
From: "DrFranken" <midrange@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 27, 2013 10:21 PM
Subject: qtemp performance oddity.


Customer with an old 720 4-way, old enough to be running V5R1.

A couple weeks ago we replaced 8 7200 RPM 8G drives with 10K RPM 17GB
Drives. Also added 768MB Memory lifting them to 2G and replaced 2741
RAID card with 4778. Disks were drained/added-no save restore. PTFs are
VERY close to the latest available for V5R1.

System had run for nearly 2 years without IPL before the upgrade.

Since the 'upgrade' the system is slower. CPU usage usually in single
digits, paging and faulting numbers are low double digits, disk percent
busys might hit 10 (15 total drives all 10K and 52% full.) WRKSYSACT and
performance tools reports show nothing odd at all. Seizes and locks are
low, disk response times are very good. IOP and IOA processor
utilizations are 10% or less. cfint shows 0.0 or 0.1% in WRKSYSACT.

Nothing at all in lic logs, problem logs, etc and yes Cache battery is
good. :-)

Any job that puts any amount of stuff in QTEMP just dogs. Some that used
to take 30 seconds take 10 minutes. Users who run tasks that use QTEMP
see more than two minutes to SIGNOFF.

I did some testing. Create file with 1M 1K Records (RPG) took 9 1/2
minutes (==1750 records per second and pushed CPU to 20%, disks to 25%
busy) Copying said file to another lib 4 1/2 minutes, copying to QTEMP 4
1/2 minutes. Clearing the other lib 30 seconds, clearing QTEMP 30
seconds. Signoff with empty QTEMP-immediate, Signoff with that file in
QTEMP-immediate. This tells me that basic stuff works fine.

Software in use is old JBA System-21. No source available but then no
changes were made.

Any ideas? Anyone recognize these symptoms?

This is odd.

--

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
--
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.


--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.