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



"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx> wrote on Mon, 22 Dec
2014 03:39:18 GMT:

On a P7, 740 8205 E6C, I currently have 18 177 SSF-2 SSD (2844
gb; 5913 controllers) in a 5887 EXP24S I/O drawer, which is
100% of my production LPAR, CEC is not used for this LPAR. We
need to add disk for a few new PF and LF that will take a
large amount of DASD. I have 6 empty disk slots in a 5887
EXP24S I/O drawer. I was planning on adding 6 775 SSF-2 SSD
(3875 gb), one new RAID-5 parity set.

How manhy parity sets do you currently have? If creating 1 new
parity set puts you in the position of having an odd number of
parity sets, this could cause an imbalance for the controllers
which could create performance anomalies.


1) I could add these 6 drives to the current sys ASP.
These 6 drive would be accessed much more heavily because of
the large difference in size. Could this be a potential
performance issue, because these would be "hot drives"? "Hot
drives" with SSD would not be as noticeable as with spinny hot
drives.


The new SSDs have better performance than the old 177GB SSDs.
This may be enough to offset the effect of mixing the two SSD
sizes.

Or,
2) I could create a new ASP for these 6 drives, and then
place only these new files in this ASP. Still have the hot
drive issue, but less impact.


But now you have to manage files in different ASPs. This can
lead to complications for DB management, journaling, etc.

3) Are there other options??





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.