Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
OAC - Pricing Info
Answers
-
Something to keep in mind (choose your terminology):
1 OCPU = 1 Core = 2 vCPUs = 0.5 CPU = 2 threads
It does not mean that 100 concurrent users need 100 threads, as the user's definition of concurrency is often "people logged in at the same time," while the system concurrency definition is "users executing a query at the same millisecond.". The first one might not mean much concerning sizing (other than the act and timing of the actual log-in operation), while the second highly impacts concurrent performance.
Even in a system with 100 concurrently logged-in users, the typical statistical likelihood of multiple users issuing a single query at the exact second is low; however, the time that the query will process and the type of dashboards (i.e., dashboards that fire multiple queries based on a single user operation) can increase those chances dramatically. The next level down is going to be where that time is spent and what type of content users are allowed to create.
Basically, the sizing of a platform analytics tool is never a one-size-fits-all and your need will also evolve as your content and users will. Based on your description, I agree with @Gianni Ceresa that 4 is the safe starting point. If you eventually get to 8, you probably have a relatively busy system (or long per-user executions). Cloud make is easier as this is not a 3 years HW buying decision, and if needed, you can also manage your cost by scaling down low usage hours/days or 'hibernate' the service on nights and weekends.
Putting all services close to each other is always the best, but it should still be ok if it is not possible. Most will not even feel the extra latency, but this is another area where mileage might vary based on a specific implementation, as even small latencies can accumulate fast to become long delays. It is just one less thing to worry about if you can co-locate it.
2 -
Does analytics per user count as the maximum number of users that can be created or logged in at the same time?
0 -
It should be named users, not concurrent users.
0 -
@Gianni Ceresa is correct; user licensing is named. I also agree with the above comment that at 450, you should consider OCPU pricing as your preferred model.
0