HP3000-L Archives

June 2004, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tim Cummings <[log in to unmask]>
Reply To:
Tim Cummings <[log in to unmask]>
Date:
Tue, 29 Jun 2004 20:54:09 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (146 lines)
I too notice pin 17 causing our system (N-Class with XP) to pause from time
to time.  Mostly when updating or adding large volumes of data.

Are there any downsides to upping the XM logfile size?

Tim

-----Original Message-----
From: Paul Courry [mailto:[log in to unmask]]
Sent: Tuesday, June 29, 2004 8:36 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] FW: XM Logfile size and XM logging of Powerhouse
subfiles


You can triple the size of the XM logfile on the private volume set no
problem.

Do not try it on the MPEXL_SYSTEM_VOLUME_SET

What this will accomplish is to cut down on the amount of time spent on pin
11 and pin 12. These pins reflect the time spent scanning your memory and
then posting the results
to disk. Someone once gave me a figure of 68 seconds to scan 10Gb of RAM as
timed on a 997/800.

You may consider the amount of time scanning memory to be a sunk cost, by
tripling the XM log file size you are reducing the frequency by which it
needs to occur.

FYI, do avoid problems I suggest you kill all sessions and jobs before you
do it.

Paul Courry


On Tue, 29 Jun 2004 11:57:51 -0400, Stanfield, Randy (Dallas, CSC) wrote:

>Sorry, if everybody gets this twice. It kicked back from the list-server.
So
>I'm sending again.
>
>I'm open to any successful tricks.
>1. N-class N4000-300-750
>2. MEMORY - 3gb
>3. xp512 SAN DISC shared between 4 HP 3000's and multiple HP9000's- current
>system has 2 volume sets
>                                   Perm   Perm           Total  Total
>Volume Set Name                   % Free  Sectors       % Free  Sectors
>
>MPEXL_SYSTEM_VOLUME_SET            33.6   203363984      34.7   210374464
>USER_SET1                          20.9   217481392      21.8   226135216
>
>volutil: showsyslog mpexl_system_volume_set
>Transaction Manager System Log Size : 52128 sectors
>volutil: showsyslog user_set1
>Transaction Manager System Log Size : 52128 sectors
>
>Any help is appreciated.
>
>Randy Stanfield
>Unisource - Dallas
>
>-----Original Message-----
>From: Craig Lalley [mailto:[log in to unmask]]
>Sent: Tuesday, June 29, 2004 8:16 AM
>To: Stanfield, Randy (Dallas, CSC)
>Subject: Re: XM Logfile size and XM logging of Powerhouse subfiles
>
>Randy,
>
>I have a neat trick that can really help (trippled the number of orders
>processed for me).  But the trick depends on the disc subsystem you have.
>
>So a couple of questions...
>
>1) what model HP3000 are you using?
>2) How much memory do you have?
>3) What type of disc are you using?
>
>Also, download the FILECNT program and make sure you don't have any groups
>with
>more than 20K files.  Let me know if you find them, because it does make a
>difference.
>
>Good Luck,
>
>-Craig Lalley
>EchoTech, Inc.
>541-619-1678
>
>--- "Stanfield, Randy (Dallas, CSC)" <[log in to unmask]> wrote:
>> Okay, two questions for the group.
>>
>> 1. is there any recommendations for the size of a XM logfiles (on system
>> volume sets vs user volumes)????
>>
>> 2. Does anybody know of a way to stop XM logging on QUIZ indexed
subfiles?
>>
>> I've been doing a lot of research on the XM logging issue of late and
find
>> discussions on how to find and tell what it is. (pin 11 or pin 17 on
>> N-class). But no real answers as to how to cut down the overhead caused
by
>> it.
>>
>> I do realize many different things are involved (image, ksam, number of
>> files in groups or directories). But how do you know at a point in time
>when
>> your system is grinding to a halt. Which one is the culprit?
>>
>> We had a system failure last week related to the number of files in a
>> directory exceeded 50,000. That was being investigated prior to the
>failure
>> but didn't figure it out in time. Since have cut the number of file to
>less
>> than 20,000.
>>
>> Still noticing pause related to the XM.
>>
>> We've asked for HP to look into the issue. But have no response as of
yet.
>>
>> Any advice is appreciated.
>>
>>
>> Randy Stanfield
>> Unisource - Dallas
>> 972-982-3621
>> [log in to unmask]
>>
>> * To join/leave the list, search archives, change list settings, *
>> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2