Re: *Max4GB or *Max1TB

Paul,

  I think you would be better off determining which access paths can be
shared (subsets of the other) and then sharing those access paths. Then
determining which Logical Files are not being used and delete them.  If
you think about it, each time a write is done to the physical file, you
have to go out and update those 250 logical file access paths.  That
takes a lot of time.

  While you might get some improvement with changing from 4Gb to 1TB as
the size, I think the number of logical files is the issue.

Pete

---------------------------- Original Message ----------------------------
Subject: *Max4GB or *Max1TB
From:    pnelson@xxxxxxxxxx
Date:    Sat, April 8, 2006 11:16 am
To:      midrange-l@xxxxxxxxxxxx
--------------------------------------------------------------------------

> I've got a client experiencing performance problems with his software
> package. Many of the files have a huge number of logicals built over them
> for various purposes. One has over 250 logicals and joined logicals. All
> of the files are defined as having an acces path size of 4GB.
>
> This system is also being hit with lots of ODBC requests that were
> permitted to be built by the previous IT manager (windoze bigot).
>
> I know how to throttle back the ODBC impact, but should I change the acces
> path size to 1TB for just the logicals or both the physical and its
> associated logicals to improve the overall performance?
>
> Thanks
> --
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978  Cell
> pnelson@xxxxxxxxxx
> --
> 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.
>
>