One of their main concerns is storage capacity and they wanted to plan and budget for at least two years worth of storage. And, guess where I found them? Capacity planning is the process of determining which server hardware will best support an Oracle Access Manager deployment based on anticipated usage. The information in this chapter provides a basis for capacity planning that helps ensure that the server hardware in an Oracle Access Manager deployment is adequate for handling peak loads.
Feel free to download and customize following free production scheduling excel template for effective production scheduling of your production unit or department in order to increase productivity. Whole template is generated in MS excel with necessary functions and formulas to make production scheduling efficient and beneficial for a business. Click the Download files below link in the Quick Details section near the top of the page to view the files to download.
Download and read the readme. MAP Toolkit Support. Since full backups in a SQL Server database contain all of the data and enough transaction log records to recover the database, the backup size is a good measurement of the required disk space. Perhaps the number of orders per month is expected to grow by 15 per cent, or the number of customer records accessed by the call centre will grow by a specific amount during a new product upgrade.
You have to understand your database inside out before you can plan capacity, especially if you're trying to predict multiple resources.
But not just the database; collecting operations statistics on your entire system will help you to determine how it is performing, and plan for the next step. Do it when there aren't any performance crunches or unexpected spikes in demand, so that you get a reliable picture of what the system normally does.
You should collect statistics on the following:. Gathering this data regularly and storing it will help you to track the increased use of data resources over time. The more historical data sets that you have here, the more accurate you'll be able to get in your predictions.
If storing your statistical data in the AWR, you can use the AWR baseline to compare multiple snapshots of data over time. Ideally, you'll want enough of these snapshots to highlight times of peak load and normal operation. You can use then use Enterprise Manager to chart that historical data. You need to find the average of these data points over time. One way to do that is to find the mean average the sum of all the values, divided by the number of values. This will take units of peak load and poor performance into account.
If you'd rather ignore that extreme data, you can use a median, in which you order the data from lowest to highest, say and take the median of the middle two values. This will remove the data that doesn't represent the norm. If you're going after specific goals or questions e. Details are beyond the scope of this document, but you can use functions such as correlations to find out how much an increase in one metric relates to the increase in another.
You might find that CPU usage is likely to be affected by the number of updates in a particular table column, for example. This could then help you to calculate the rough number of updates to that particular column permitted by a certain number of CPUs, at a specific CPU usage rate.
Excel spreadsheets are a common way to calculate these results, and there is a variety of pre-baked Oracle capacity planning spreadsheets available for sale online. Your thresholds are levels of system usage beyond which you don't want to move. Thresholds can be set on all kinds of metrics in Oracle, such as cumulative user logins, for example.
These thresholds will help you to monitor when your resource capacity is starting to fall behind. As the number of critical alerts increases, it'll be a good sign that your capacity planning model needs to be revised, and new resource potentially added.
Capacity planning isn't the easiest of tasks for Oracle DBAs, and statistical modelling is never a completely sure thing. The further out you try to plan, the less accurate your details may become, which is why regular revision of your statistical data and recalculation of capacity baselines is a good idea.
This technical know-how, complemented by regular communication with business users to see what new demands are coming down the pipe, will help to keep your database ready for the challenges that a healthy business will inevitably throw at it. Most importantly, it will keep you in control of your systems. This is a far better place to be than the alternative. No one wants to be thrown into reactive mode as they scurry to fix performance problems that were months in the making - if only they had the foresight to spot them.
Lloyd's, the world's largest insurance marketplace, has contracted DXC Technology to digitise its processes as part of a multi-year effort to move on from a largely paper-based, analogue way of working.
The London insurance market accounts for 7. It is made up of more than 50 insurance firms, plus registered brokers, and a global network of 4, local cover holders. The capacity management plan should include a determination on whether the CPUs should be used more efficiently for the nominal load, or should there be some extra capacity for a burst of activity. Once you have defined your performance objectives, measured your workload, and identified any bottlenecks, you must create and implement a capacity management plan.
The goal of your plan should be to meet or exceed your performance objectives especially during peak usage periods and to allow for future workload increases. To achieve your performance objectives, you must implement your management plan and then continuously monitor the performance metrics as discussed in Chapter 4, "Monitoring Oracle Fusion Middleware".
Since no two deployments are identical, its virtually impossible to illustrate how a capacity management plan would be implemented for all configurations. Capacity planning is an iterative process and your plan must be calibrated as changes in your workload or environment change.
The following section provides key factors that should be addressed in the plan:. There is no single formula for determining your hardware requirements. The process of determining what type of hardware and software configuration involves assessment of your system performance goals and an understanding of your application.
Capacity planning for server hardware should focus on maximum performance requirements. The hardware requirements you have today are likely to change. Your plan should allow for workload increases, environment changes such as added servers or 3rd party services , software upgrades operating systems, middleware or other applications , network connectivity and network protocols.
Memory requirements are determined by the optimal heap size for the applications you are going to use, for each JVM co-located on the same hardware. Each JVM needs up to MB in addition to the optimal heap size; the actual impact to performance depends on the JVM brand, and on the type of application being run.
For example, applications with more Java classes loaded need more space for compiled classes. It is recommended to reserve some memory for the Operating System, IO buffers and shared-memory devices. As part of your performance monitoring and benchmarking procedures, you should determine how many and what kinds of processes are executed and determine if your hardware meets the requirements for your specific JVM.
Using multiple managed servers across multiple nodes in a clustered configuration is recommended for both high performance and reliability. It is important to note, however, that having multiple managed servers may mean using more memory which can enable some applications to optimize certain operations in-memory, therefore reducing impact of disk, database and network latency. To maintain sustained performance, you must ensure that your existing database can scale with the increases in capacity planned for the application server tier.
Tuning the database parameters and monitoring database metrics during peak usage, can help you determine if the existing database resources can scale to handle increased loads. You may need to add additional memory or upgrade the database hardware configuration.
In some cases, however, you may find that the database is still not able to effectively manage increases in load, even after increasing the memory or upgrading the CPU. Oracle RAC configurations not only provide enhanced performance, but they can also improve reliability and scalability.
Note: The information contained in this chapter is meant to provide an overview of various techniques that can be used to develop an effective capacity management plan. Section Is the workload likely to increase? Ideally you have information about the levels of activity that components of the application are expected to meet, such as: The anticipated number of users. The number of concurrent sessions.
0コメント