MoreVRP Vs. ORM - Oracle Resource Manager
 

Oracle Resource Manager is an internal Oracle solution that allows you only to prioritize  between databases users (rather than allocate resources). It starts prioritizing the CPU consumption only, of specific transactions, once your machine hits the 100% CPU.In most databases, being in 100% is unsafe.

In addition, in most databases, Heavy IO consumers (such as reports) doesn’t take your machine to the 100% CPU utilization and therefore – when it comes to I/O bottlenecks, ORM is useless.

ORM gives you the ability to allocate your resources based on databases users only while most application nowadays identifies themselves to the database as a single user to the database.
Allocating resources to a specific databases users under these circumstances, is a matter of 15-20 clicks (or massive scripting) in ORM, while only 1 mouse click in MoreVRP. In addition ORM doesn’t let you do that in real-time to an already running transaction.
 
Unlike ORM, MoreVRP allows to:

  • Resource Bandwidth Allocation (rather then just prioritization)
  • Working below 100% CPU
  • Stabilizing your system while never letting it get to the 100% utilization.
  • Manage both your CPU & IO per transaction.
  • Real-Time Monitoring
  • Affecting already running transaction in real-time. (Ad hoc and rule based)
  • Easy to Use (Mouse clicking rather than scripting)
  • Allocated resources based on your business characteristics (transaction, time
  • of the day, Applicative module, program, PC name…) and not only by database users.
  • Low Footprint
  • Manage QoS of users on the same databases, and between several databases.
  • System processes Management & Control
  • Recommendations, SLA & QoS reports
Excellent  / Very Good   / Good   / Fair   / poor  /  N/A
 
Capability

MoreVRP

ORM

Virtualization at the transaction level

 

 

Bandwidth allocation (unlike prioritization)

 

 

Real Time allocation of resources on demand

 

 

Ability to prioritize between different databases on the same machine

 

 

Real-time performance analysis through dashboard

 

 

Managing the CPU & IO resources per transaction

 

 

Managing other system processes (not database transactions)

 

 

Footprint on the database server (5 star is best)

 

 

Ease of management

 

 

Managing Qos (Quality of Service) of important users

 

 

Stabilizing the server not allowing it to get to 100% utilization

 

 

Flexibility – configure rules based on specific SQL, Username, Time…

 

 

Supporting Multiple databases (Oracle , SQLServer, DB2)

 

 

Repository for historical performance analysis and automatic suggestions

 

 

 
 
בניית אתרים