Re: x5-2 1/8th putting io hard limit on one of pdbs and WBFC as a bonus q
Date: Sat, 4 Jun 2016 11:35:53 -0400
Message-ID: <CACNsJncMh224har6Bom441AEuHAa1Av5Q=2bXBSYcuZSmF_3dQ_at_mail.gmail.com>
Answers below inline:
1 Performance_profiles (inherited from CDB ) Questions:
- do I have to include all other DB (cdbs+PDBS) in IORM plan even if I dont care about them in terms of I/O performance ?
<-- make sure to setup a DEFAULT share for your other or future databases, and you can also impose a LIMIT on them. PDBs inherit from the CDBs so you only deal with them from the DBMS_RESOURCE_MANAGER package and not on cellcli.
<-- also you can mix Profiles and Inter-DB in a DBPLAN in cases where you have an older version of the database (mix of 12c and 11204)
ALTER IORMPLAN DBPLAN=( (name=gold, share=10, limit=100, type=profile), \
(name=silver, share=5, limit=60, type=profile), \
(name=bronze, share=1, limit=20, type=profile), \
(name=demo, share=10, limit=100, type=database), \
(name=default, share=2)
);
- demo is 11204 database with TYPE=database
- the rest of DBs gets a share of 2 2. shares + utilization_limit same question as above ?
What whould You recommend as a best solution in such way stated problem (throttling I/O of one PDB only in terms on real hard limit like 80% I/O capacity of the cell ) .
<-- I would go with SHARES first. Just to keep it simple as possible. And if the requirement is to really limit the IOs then I would impose the UTILIZATION_LIMIT <-- make sure you that you track the CPU breakdown and end percentage utilization across databases and consumer groups when you impose the SHARES and the LIMIT/UTILIZATION_LIMIT. it gets pretty hairy when you are dealing with a lot of databases+PDBs so making a spreadsheet of who gets what will make the designing easier. that's why I start with SHARES first and impose UTILIZATION_LIMIT next.
here https://github.com/karlarao/talks/archive/eco_2015.zip there's a spreadsheet "DBRM IORM Testcase Matrix.xlsx", check out the "FullModelExample2", "IORM architecture & design", "IORM matrix" sheets. that will help you with designing the IORM+RM plan.
Bonus question :
In terms of switching into write back cache in rolling fasion , does the 3
cell nodes still allows me to go in rolling mode without crashing the
running instances ?
<-- yes
-Karl
On Sat, Jun 4, 2016 at 8:33 AM, GG <grzegorzof_at_interia.pl> wrote:
> Hi,
> we are on x5-2 1/8 (3storage + 2 DB nodes) rack, GI + RDBMS is 12.1.0.2 .
> Trying to put IO constraints on one of PDBs like 80% hard limit for
> getting Cell I/O performance .
> As far as I can tell only two options there :
> 1 Performance_profiles (inherited from CDB )
> Questions:
> - do I have to include all other DB (cdbs+PDBS) in IORM plan even if I
> dont care about them in terms of I/O performance ?
>
> 2. shares + utilization_limit
> same question as above ?
>
> What whould You recommend as a best solution in such way stated problem
> (throttling I/O of one PDB only in terms on real hard limit like 80% I/O
> capacity of the cell ) .
>
> Bonus question :
> In terms of switching into write back cache in rolling fasion , does the 3
> cell nodes still allows me to go in rolling mode without crashing the
> running instances ?
>
> Regards
> GG
> > > > > > > > >
> --
> http://www.freelists.org/webpage/oracle-l
> > >
-- Karl Arao Blog: karlarao.wordpress.com Wiki: karlarao.tiddlyspot.com Twitter: _at_karlarao <http://twitter.com/karlarao> -- http://www.freelists.org/webpage/oracle-lReceived on Sat Jun 04 2016 - 17:35:53 CEST