|
Not a new recommendation at all. Usually when a system is preloaded or
built by IBM, they do not know your needs, therefore they usually just
create a 400Gb unit and then let you configure the rest of the storage.
That’s done in DST/SST with (V7R3 macros) or V7R4+ with the menu options.
It’s likely the CSR (CE) was not IBM i trained (as opposed to AIX) so a
large storage space was OK since AIX likes that type of storage.
If that nvme was set up as one unit (mirrored) that will affect
performance in a big way, but is partially overcome by the speed of access
to storage. It is possible to fix it but it will require some surgery to
do it.
Adding the new units will go a long way to fixing that, however if the
large storage units are left on the system, it will preferentially go to
the biggest storage unit with I/O (long standing issue in storage
management) so in the end, you may need to fix that before you get to the
performance standard that makes you happy. The biggest impediment to
getting that done will be if the load source is huge, changing that is the
real problem and requires some real serious system knowledge to pull off.
Jim Oberholtzer
Agile Technology Architects
On Jan 31, 2024, at 2:23 PM, Gad Miron <gadmiron@xxxxxxxxx> wrote:then
Thanks Stefan, Jim, Patrik
Having used the Multi-Name-Beast (AS400/iSeries/Series5...) for longer
I care to rememberhave)
I know the golden rule "The more disk arms the better"
What I want to know is what performance gain to expect.
However,
having opened a case at IBM I was asked to supply a SYSSNAP (which I
for them to evaluate. (they referred me to Expert Labs team first butthen
reconsidered)that
Let's hope.
Thanks again guys.
Gad
P.S.
Since this is a fairly new machine (6 months) I wonder why the IBM CE
installed itlist
did not configure those multitudes Namespaces right then.
Seems like a new recommendation for NVMes
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.