Re: Exadata Cloud at Customer Pricing

From: Ls Cheng <exriscer_at_gmail.com>
Date: Tue, 21 Jan 2020 20:10:35 +0100
Message-ID: <CAJ2-Qb-r+dxEoK8pgagY8kJgVJYPdnh16-7yqqRR=3AruojgYg_at_mail.gmail.com>



Thanks a lot Ghassan

On Tue, Jan 21, 2020 at 6:58 PM Ghassan Salem <salem.ghassan_at_gmail.com> wrote:

> If you don't have an ExaCC now, and want to use one, you'll get a gen 2
> machine. This is managed like any resource on the Oracle Cloud
> Infrastructure (OCI). You can scale-up/down OCPUS of a VM via console, or
> via APIs. So, in your case, you can have an api call to scale up before
> starting your batch, and scale down after it. As for the DB CPU_COUNT, it's
> like on any other system: if you do not specify anything in your spfile,
> then the DB will pick up the new number a few seconds after you change it.
> Regarding unexpected high load, all you can do is have some monitoring
> script running and do the scale up/down when needed. I'm not sure there's a
> plan to implement auto-scaling on ExaCC, as is the case in autonomous DB,
> but you never know. Things keep improving in the cloud space.
>
> rgds
>
> On Tue, Jan 21, 2020 at 6:42 PM Ls Cheng <exriscer_at_gmail.com> wrote:
>
>> Hi Ghassan
>>
>> Currently we only use roughly 45% CPU per node in peak time (we have 22
>> Cores per EXA database node) but the runqueue is around 40 due to high
>> number of processes. If we move to Exadata CC I guess during peak time (4
>> to 6 hours per day) I must scale to 22 core per node at minimum otherwise I
>> will have CPU contention. Is the scaling automatic and dynamic? How does
>> the database deal with the change of CPU_COUNT? I also have some unexpected
>> peak time in different time of the day (sometimes the business users run
>> batch without notifying the database team), how Exadata CC deal with such
>> situations?
>>
>> TIA
>>
>>
>>
>> On Tue, Jan 21, 2020 at 6:26 PM Ghassan Salem <salem.ghassan_at_gmail.com>
>> wrote:
>>
>>> The enabled CPUs are charged, used or not. BUT, you can enable a small
>>> number, and scale-up/down as you need. If, for example, you went from 20
>>> ocpus to 30 for 2 hours, then back to 20, you'll be charged 10 ocpus for 2
>>> hours.
>>>
>>> On Tue, Jan 21, 2020 at 6:20 PM Ls Cheng <exriscer_at_gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Has anyone got practical experience with Exadata CC and know how they
>>>> charge OCPU?
>>>>
>>>> Does Oracle charge per number of enabled OCPU or the CPU cycles used?
>>>> In the second case for example there are 40 enabled OCPU but if the usage
>>>> is average 20% per month only 20 OCPU is charged?
>>>>
>>>> TIA
>>>>
>>>>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jan 21 2020 - 20:10:35 CET

Original text of this message