This blogs succeeds the one on determining the sizing KPIs. For more information on Quick Sizer results, see. Quick Sizer for Initial Sizing As mentioned before, initial sizing, when you have only a vague idea of the expected workload is dominated by a user sizing. Sizing for your concurrent active users is pretty straight-forward in the Quick Sizer. It only takes into considerationusers that are logged on and consume system resources, for example in the Enterprise Portal or in mySAP CRM. In some solutions the Quick Sizer requires you to specify in which application the users work predominantly, in mySAP CRM, for example, it distinguishes between Opportunity Management, Activity Management, sales transactions or service transactions. In some user sizings you are requested to specify an activity profile, for example: how many users have a low, medium or high activity?
The activity patterns merely expresse the number of screen changes per user per hour. A highly active user, for example, corresponds to a power user with a think time of 10 seconds between screen changes. When youve entered the user information and choose calculate result, youll get the following information for each SAP solutionThe required. CPU power in SAPS (hardware-independent, see above). Disk space in MB. Memory in MB (in units of 256 MB) For your convenience, there are categories for the disk and CPU result that indicate whether you are in a small or medium sized environment. As explained above, the initial sizing is only a very rough ballpark estimate which is why I would not recommend relying only on a user-based sizing if the result is higher than 5000 SAPS.
User sizing per se is very inaccurate in the sense that it does not account for background processes, interfaces, and so on, and therefore the Quick Sizer provides high sizing results as compared to throughput sizing. So if you happen to do both user sizing and throughput sizing and find that the results deviate significantly, this can be either because you have specified a user activity that is too high or because the throughput sizing is more accurate. The Quick Sizer does not offer user sizing for all applications. The Exchange Infrastructure (XI), for example, has no user sizing. As a pass-through engine, it has no dialog load. For this, we provide an initial throughput sizing for SAP XI. Quick Sizer for Advanced Sizing When you are a little more familiar with how SAP software represents your business applications, youre ready for advanced sizing based on throughput numbers.
This sizing is usually more accurate for several reasons. The Quick Sizer contains some 120 sizing elements for throughput sizing that reflect the most common and potentially most load-consuming transactions and business applications for mySAP.com. The information the Quick Sizer wants to know follows a simple pattern: Number of objects (projects, printed documents, sales orders or travel receipts) per year, number of sub objects (networks, activities or line items) and how many months these data will remain in the database until they are archived. If you enter this information and choose calculate result, the Quick Sizer renders basic CPU and disk requirements (remember that memory is dominated by users). This sizing method is called average sizing from which you can build on towards a peak sizing. The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing). You enter the number of objects and sub objects and specify the time period when these objects are being processed, for example: The payroll of 200,000 employees from 2 am to 4 am.
If this run coincides with the nightly background run for the materials requirements planning, the Quick Sizer shows the peak CPU requirement. When we say peak sizing, we mean the peak over all individual sizing results. If the average sizing for a sizing element renders 1000 SAPS, and the peak sizing 1200 SAPS, the overall result of the sizing is 1200 SAPS. If the peak sizing should render a value below the average sizing (if specified by you), the Quick Sizer issues a message. You can then go on redefining your sizing:.
For example, you can enter how often an object is changed per year or per peak phase. This influences the CPU sizing. You may also want to change the average workday. Per default, the Quick Sizer assumes that an average workday ranges from 9am to 6pm, which you can easily change, thus influencing the CPU result. The Quick Sizer also assumes 220 work days per year as a default.
If you adapt this value to your needs, this also influences the CPU result for the average sizing. By the way, the number of workdays also influences the disk sizing for the users. You can extend the average sizing by allowing for multiple averages. For example: in a customer system, orders are created in mySAP CRM, by handhelds and by Interaction Center users. The orders are transferred to the ERP system for full order processing.
By adding lines, you can distinguish between the orders that were originally passed on from the handheld scenario and the Interaction Center. To make this information transparent you can add a short text to each line.
The Quick Sizer will add the averages and calculate the result for you. One function that, strictly speaking, is not relevant for the sizing calculation is the archiving flag. If you enter this, the Quick Sizer checks whether an archiving object for this sizing element exists. Below find an example for a simple sizing of travel receipts. The number of objects field contains the number of travels, and the Line items field refers to the number of receipts. Figure 1: Example for simple average sizing.
If you use all these functions, you can get a pretty accurate representation of the hardware required to run the business. However, this sizing will always be based on standard processes that SAP has designed and measured. Quick Sizer for Expert Sizing Expert sizing makes the utmost use of the standard functions of the Quick Sizer. Expert sizing is for customers whose business requirements encompass the rule of 80/20 (80% of the load is created by 20% of the transactions), first-and-foremost because of custom modifications, system to system data exchange, customization, and so on. One standard function of the Quick Sizer that can be exploited for expert sizing is the possibility to set multiple averages against multiple peaks.
The Quick Sizer always checks which sizing method renders the higher CPU value, average or peak. Using a function called ID for identification, you can specify which averages are calculated against which peaks. This is very helpful for complex scenarios, for example in the retail business or in the example above, where orders come in from very different sources. The figure below shows you an example. CRM-SLS is the CRM sizing element sales orders, A specifies average sizing, Y stands for objects per year. Figure 2: Example for multiple averages.
If you do not enter anything in the ID column, all averages are added and calculated against all peaks, which may blur the result. Also, you can use rules of thumb mapped to the Quick Sizer to account for special processes. For example, there is a rule that says to account for additional load caused by RFC processing, add 10% load on the sales orders that are transferred to another system. In this case, you would add an additional line for peak, enter 10% of the number of orders and add in the short text field additional RFC load.
Figure 3: Example for multiple averages against mutiple peaks and rule of thumb. In principle however, expert sizing can only take place if the customer already has a test system up and running. Then we recommend using standard SAP system monitors to obtain sizing relevant information such as CPU time, table size and memory consumed per business process. Ezvid movie maker offline installer. If you have this information you can relate it to the Quick Sizer. For example, you have written your own sales order application and your measurements show that this is 1.5 times as expensive as the Quick Sizer sales order. Then you can simply exploit the functions of the Quick Sizer for your own software by applying a factor of 1.5. Quick Sizer and GoingLive SAP Support offers the GoingLive Check (GLC), and one of the features of GoingLive (GL) is the plausibility check of the sizing where the Quick Sizer entries and sizing results are checked against the performance capabilities of the hardware the customer has purchased.
This can be done on the basis of the sizing data. In some cases, GLC offers additional checks if certain business processes are not (yet) included in the Quick Sizer. When you are ready, you can simply set the status of your sizing project in the Quick Sizer to GoingLive. Then the ownership of the sizing projects changes to GoingLive, to SAP Support, that is.
You yourself are not able to make modifications to this project until SAP Support has changed the project status to in process after GL. That way, SAP and customer can work together on the hardware plausibility check relying on the same data.
If you set the project to final, no one can change the project anymore. Interpreting Quick Sizer Results For reasons of better analysis, the Quick Sizer allows you to analyze sizing results at very different levels of detail. Here are the most important ones. Result at solution level By default, the Quick Sizer displays the sizing result by sizing method (user and throughput) and by SAP solution, for example mySAP ERP or SAP Netweaver. For each solution the Quick Sizer displays the required:.
CPU power in SAPS (hardware-independent, see above). Disk space in MB. Memory in MB (in units of 256 MB) For easier analysis, there are also categories provided. If you only have a user-based sizing and if this result exceeds category 7, you should either perform a throughput sizing or contact your hardware vendor or SAP.
If you did both sizing methods and the category exceeds 15, you should also contact the hardware vendor or SAP for help. For your convenience, you can display a chart of the CPU load over the day.
Result at software component level To plan your system landscape it is helpful to know the hardware requirements for each software component, for example Enterprise Core Component (ECC) or Portal Server. On this result level, the results are also split to reflect load on the application server and on the database server, for example. Display all inputs and all results This function is predominantly useful for documenting the sizing project as it contains all the data you entered and all the results of the Quick Sizers. With the print function you can download this information to save on your PC. This function is also helpful if you want to analyze the sizing data in more detail. More often that you think you can detect erroneous entries by simply doing a plausibility check on the highest CPU or disk contributors.
This result level also provides detailed information on the top disk contributors, the table names, the projected growth, available archiving objects, and so on. For more information, see. Suzanne, for FI-CA, I notice you now have added Utilities to the Insurance model that you had before. I want to size PSCD (Public Sector FICA flavour). We used to use the Insurance one for this.
I have 3 Questions: 1. Do you intend to do a specific one for PSCD & if so, when? If not, would it not be a good idea to make Insurance easier to use, by, in the help, to specify which PSCD metrics map to which Insurance metrics? For the new Insurance model, a) the master data metrics (BP’s, CA’s i-objects) have now disappeared- where do we enter them? B) In “SubLedger”, is the “Payments” metric absolute or “payments per posting doc”? Thanks in anticipation, Mike.
Hello Susanne. I’m not sure if this is the right place to ask, but it’s quite urgent. I’m trying to input to BW SEM-BPS-2, but the values don’t meet the requirement, which is 900,000 after some calculations inside the QS. These values are the real numbers taken from an active system.
It seems the system is running fine, but I need to calculate SAPS for the correct sizing. I appreciate if you could provide a solution. Input values can’t be changed because as I said, the values are taken from an active system. Thank you in advance for your support!! Hi Kentaro, there are two answers to your question. 1: Apparently you are re-sizing you system, either you are adding load or upgrading.
For this exercise you should never use the Quick Sizer but interpret your live data. For the procedure of re-sizing, please see service.sap.com/sizing - sizing guidelines - general - “re-sizing”. 2: not knowing your inputs, it may be that you already entered multiplied data that the Quick Sizer would usually multiply taking different input fields into consideration. Best regards, Susanne. Hi Ayak, Let me try to answer your questions.
1: Is your question: “How can I insert a new sizing element”? Sizing elements are predefined by SAP and cannot be created on the fly. They represent business objects or business scenarios that representing sizing-influencing patterns. 2: Is your question: “Why are sizing elements not aligned to transaction codes?
The Quick Sizer is targeted at initial, i.e. New sizings, where users are not familiar with transaction codes but rather think in scenarios or business objects. Hi Francois, There is a small documentation in the Service Marketplace in the area of “using the Quick Sizer”, Quick Sizer for beginners where these fields are explained.% Changes/Displays affect the CPU calculation only. 1) This is a very general question.
There is no particular recommendation other than: if you can estimate on average, how often a document is being changed, just enter 100 for each change. 2) Use cases depend very much on the customer. There are certainly objects that are changed more often than others. Projects ought to be changed hundreds of times. 3) printing is not included, you can use BC print, but please note that BC Print reflects SAP scripting.
![Learning Learning](/uploads/1/2/3/7/123756030/694070440.jpg)
Best regards, Susanne. Hi Mary Jane, I think there is a small misunderstanding. Sizing is all about peaks and providing sufficient hardware for peak usage. When you say: “ of course my peak sizing is less than my daily sizing” Frankly, this doesn’t make sense from a sizing perspective. As the description in the blog says: “The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing).” The Quick Sizer shows this error message when the result for the peak sizing is below the average in your case the hours specified are between 8-10. Best regards, Susanne.
Hi Mary Jane, I think there is a small misunderstanding. Sizing is all about peaks and providing sufficient hardware for peak usage. When you say: “ of course my peak sizing is less than my daily sizing” Frankly, this doesn’t make sense from a sizing perspective.
As the description in the blog says: “The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing).” The Quick Sizer shows this error message when the result for the peak sizing is below the average in your case the hours specified are between 8-10. Best regards, Susanne. Hi Susanne, Could you suggest,which all aspects we need to consider for EP7 sizing on Unix boxes? I have gone through quicksizer tool, but it considers only concurrent users,avg think time, iviews as inputs based on which the calculation of sizing is difficult as we need to take into consideration infrastructure specifications like.
High availibilty, load balancing and also application usage, implementation of KM, collobration other componenents of portal, NWDI implementation, Trex and integration with back end SAP systems, portal access for external user in addition to intranet users. May I know, how do we analyse the above aspects as I mentioned for sizing or quicksizer is the only tool for sizing? Regards Praveen.
Hello, I asked a BI colleague. Here’s the answer: The peak data load describes the amount of records than need to be loaded into the first persistence level of BI in a given time frame.
Quick Sizing Tool Sapling Learning
In detail this means that it includes extraction from the source system, transfer of the data to the PSA, and then either update into an InfoCube or into a DataStore object (including activation). If you plan to have several data staging layers, then you should (as a rough estimate) add the same amount of records for each additional stage, e.g. Extraction of 1 million records to PSA, DataStore and then from DataStore to InfoCube would render twice the amount of records extracted from the source system. Best regards, Susanne. Hi Suzanne, SAP recently changed its SD benchmark from 2 sec to 1 sec response time.
So, now we have vendor benchmarks with 2sec-SAPS and with 1sec-SAPS. Has this change been reflected in quicksizer?
If not, when quicksizer results are, for example, 10,000 SAPS, if I select a platform with 1-sec benchmark, I will be oversizing. Conversely, if quicksizer now reports 1-sec SAPS and I select a platform with a 2-sec benchmark, then I will be undersizing it (40% I estimate).
![Quick Quick](/uploads/1/2/3/7/123756030/795034877.jpg)
Is this correct? Are there any plans to normalize this / Instructions for users? Regards Glen. Hello Glen, the Quick Sizer team states the following: In the benchmarks you need to factor in a wait time of 10 seconds between the interaction steps. This means for example, that 6000 steps in the old Benchmark take about 11/12 of the time compared to the old Benchmark, and not 50%.
This results in a difference of about 5% for the SAPS of a hardware. We carefully discussed the question, whether this (and other changes in the SD benchmark) should have an influence on the existing sizing calculation in the Quick Sizer.
We decided to keep the values for the majority of the sizings, with the exception of CRM, were we adjusted the calculation as of March 2009. Best regards, Susanne. Hi Susanne, I have a client who want to implement Enterprise Portal.
Basically, it is just to be used as a front-end to their backend ECC/SRM/BW systems to avoid having to logon multiple times via the SAP GUI. There won’t be any Business Packages loaded or any fancy development or any use of KM, at least not initially. My question is which area of the Quicksizer should I be using? The only scenario which seems appropriate is the ‘SAP Netweaver - Portal and KMC’, and then use the NW-EP-URL element within that. Is this correct?
I can’t see any other portal-related scenarios. Kind regardsJohn.
As companies become more and more price conscious, they are realizing just how important it is to plan and budget their hardware expenditures. After all, a poorly planned hardware purchase will only result in added costs and headaches down the line. Key to a successful hardware project is accurate hardware sizing.
Too many people rely on guesswork when choosing their hardware, either overstating or underestimating the power or memory that their solution installations will need. By determining your sizing requirements before you shop around for hardware, you’ll ensure that your hardware purchase will meet your business and performance requirements. You’ll also be able to lower your costs and reduce total cost of ownership. Just consider the costs of unused hardware — beyond its initial price, you also have to account for the ongoing energy and maintenance costs it will accrue. To help you determine your hardware sizing neesapds, SAP provides Quick Sizer, a self-service tool available for free on SAP Service Marketplace that can be used to predict the hardware capacity needed to run your business smoothly (see sidebar).
In short, this tool can help you translate your business requirements into hardware requirements. Quick Facts About Quick Sizer. Quick Sizer has been available as a free self-service tool since 1996. It was developed in cooperation with SAP’s hardware partners to help customers determine the parameters of their hardware needs. Approximately 30,000 users in about 50,000 sizing projects take advantage of this tool each year. Implementation, hardware, technology, and hosting partners, as well as SAP Consulting, Sales, and Support organizations, all use this tool.
You can only use Quick Sizer for the initial sizing of SAP standard solutions. Quick Sizer should be used iteratively — so if your data becomes more precise, you should update and adjust your Quick Sizer project, too.
You’ll find an earlier introduction to the basic functionality and terminology around Quick Sizer in “,” by Susanne Janssen in the January-March 2006 issue of. In this article, we take a deeper dive into how to use Quick Sizer and what to do with your results. Quick Sizer: When to Use It Companies can use Quick Sizer if they are planning a new installation of SAP software (an initial sizing) or if they want to add new SAP software to an existing SAP solution landscape (a delta sizing).
Quick Sizing Tool Saplings
Say your company wants to implement SAP CRM. You’ll need to perform an initial sizing to determine the hardware requirements for this solution landscape.
Using the Quick Sizer tool, you’ll gain guidelines for your hardware requirements — including required CPU time, disk size, and memory size — so you can start planning your hardware landscape. How to Use Quick Sizer: 4 Key Steps Let’s uncover how a company preparing to implement SAP CRM can use Quick Sizer to ensure that its hardware will support the application — and what it can expect to learn from the results. Step #1: Create a New Project in Quick Sizer To use Quick Sizer, you’ll first need to set yourself up as an S-user in SAP Service Marketplace (if you haven’t already). Then visit, where you’ll see the Quick Sizer entry screen (see Figure 1). For first-time users, the link labeled “Quick Sizer for beginners” may be helpful.
It takes you to documentation that explains all of the functions of Quick Sizer. The entry screen also offers several options for managing your projects:.
To create a new project, enter a new project name in the “Project Name” field and click on “Create Project”. To change or view an existing project, enter the project’s name in the “Project Name” field and click “Change Project” or “Display Project”. To display a list of all projects you’ve worked on before, choose “Show my projects”. To copy an existing project’s data into a new project, choose “Create with ref.”. This article’s example takes you through the process of creating a new project. Figure 1 Entry screen for the Quick Sizer tool Step #2: Complete the Quick Sizer Questionnaire Once you set up and name a new project in the entry screen, the Quick Sizer tool will open.
Here you will see a navigation tree (see the left side of Figure 2) where you will find a list of all SAP solutions that are available to be sized. When you click on a solution name, you will see a questionnaire (see the right side of Figure 2) specific to that solution. The data you enter into this questionnaire will remain available online so you can use it for sizing verifications during your implementation project. Figure 2 SAP CRM Sales questionnaire in Quick Sizer Note that Quick Sizer does not contain questionnaires for all SAP applications. This is because, when analyzing the resource consumption of a production system, we’ve learned that roughly 80% of the capacity requirements are occasioned by 20% of the transactions (the 80/20 rule). If you cannot find an application in Quick Sizer, it is likely because:.
The application’s performance impact is negligible. The application is very new — in this case, SAP can help you perform a one-on-one sizing project. The application may be able to be sized with a simple t-shirt sizing algorithm. Quick Sizer does contain questionnaires for most SAP Business Suite solutions, as well as for several industry solutions (like SAP for Banking) and specific SAP NetWeaver components (like SAP NetWeaver Portal).
You can also use the “Search” functionality to find the right questionnaire for your needs. For our example, in the left-hand navigation field, you would select SAP Business Suite SAP CRM CRM Sales. You’ll then see a questionnaire. Most questionnaires — like our example in Figure 2 — will have multiple input tables for the two different types of sizing, throughput-based and user-based. In the user-based sizing table (Table 1 in Figure 2), you will need to enter the number of users that concurrently work with the solution you are sizing (in this case, we’ll enter 200 SAP CRM Sales users into the “SLS-USER” field).
In the following sidebar, we’ve offered helpful guidelines on how to categorize your user activity. If you are unsure of how active your users are, we recommend entering this number under the “Medium activity users” column. User-Based vs. Throughput-Based Sizing: What Does It All Mean? User-Based Sizing User-based sizing, as the name suggests, determines your sizing requirements based on the number of users working with the system.
To determine this number, you will need to fill out a table (Table 1 in Figure 2) that defines concurrent active users (users that are logged on to the system and that consume system resources within any given time period). In the Quick Sizer questionnaire, there are three categories of users that represent typical user activity patterns:. A low-activity user processes an average of 12 interaction steps per hour.
A medium-activity user processes an average of 120 interaction steps per hour. A high-activity user processes an average of 360 interaction steps per hour If you have fewer than 200 active users, filling out only the user-based table will likely be sufficient to estimate your hardware needs. If, however, you have more than 200 active users, you’ll need to fill out the throughput-based sizing table as well as the user-based one. (Note: This is only true if both sizing approaches are available in your questionnaire.) Throughput-Based Sizing Compared to the more straightforward user-based approach, the throughput-based approach allows you to define more variables. You can include additional parameters like business objects used, and also account for peaks and averages.
For simple throughput-based sizing, you only need to fill in three input fields in the average row (in Figure 2, this is the third row of Table 2, called CRM-SLS / A): “Objects” (the number of business objects that have to be processed per year), “Items” (the number of items per object), and “Mon.” (the number of months the data remains in the database). For more advanced throughput-based sizing, you will also need to fill out the peak row (the fourth row of Table 2, called CRM-SLS / P).
Here you enter the number of objects that have to be processed during peak times, the number of items per object, and the timeframe in which this data has to be processed. The figure summarizes the characteristics of these two sizing methods. Figure Overview of user-based and throughput-based sizing approaches In the throughput-based sizing tables (Tables 2 and 3 in Figure 2), you will need to enter the number of objects that the solution you are sizing will need to process in a certain timeframe.
For this example, let’s say that your 200 sales users process approximately 2,000,000 sales orders (enter this information in the “Objects” column), with 10 line items per year (“Items”), and that the data must be kept in the database for six months (“Mon.”). It is very important to note that the results you get from Quick Sizer will only be as good the data you enter into the questionnaire. That’s why it is critical for the different parties involved in a sizing project to collaborate. For example, IT departments that are determining the input values for Quick Sizer should contact the user department to collect pertinent information, ensuring that they enter the input data that best describes the business. Once you’ve entered all relevant input values, click “Check” to scan for input errors.
Then, click “Calculate result.” Step #3: Analyze Your Quick Sizer Results Based on your questionnaire inputs, Quick Sizer will then calculate the required system resources — such as CPU power, memory, database disk space, and disk I/Os — that your hardware will need to support your new solution. To analyze these results, you can break them down into seven distinct result levels, which provide different perspectives on the sizing result (see the “Result level” drop-down box at the top of Figure 3).
Most companies will only ever use three of these result levels: “Software components,” “Results, statistics, inputs,” and “SAP solutions.” Figure 3 Quick Sizer results page With “Software components,” you can get specific sizing results for any separately installable deployment unit. If you are deploying SAP ERP, for example, you could see the sizing results for the SAP ECC server.
“Results, statistics, inputs” contains all the data you entered into your questionnaire as well as all of Quick Sizer’s results. While this amount of information may look overwhelming, it is useful for documenting the sizing project. By default, however, Quick Sizer will display the “SAP solutions” sizing results, as seen in Figure 3. In this case, Quick Sizer has calculated that the company will need hardware that supports 4,600 SAPS. For quicker, easier analysis, there are also result categories in the “CPU cat.” column, ranging from small (S) to extra large (XXL). The user-based and throughput-based results you get from Quick Sizer should not be added together. In most cases, the results will be similar numbers.
If there is a strong divergence between both results, there are probably entry errors in the questionnaire. Step #4: Use the Results to Size Your Hardware Now that you’ve used Quick Sizer to generate your hardware parameter guidelines, you can start looking for hardware that fits your needs. In our example, we’ll need hardware that supports 4,600 SAPS. Note that Quick Sizer results also include requirements to support Unicode (as of December 2006). If you want to compare Quick Sizer results with non-Unicode benchmark results, you can deduce 10% processing capabilities from the final result. For example, our results rated 4,600 SAPS. If your configuration is running a non-Unicode benchmark, however, it is likely to achieve 4,140 Unicode-SAPS.
You can then take your results and visit to browse suitable hardware options. You can also use your Quick Sizer results in conjunction with SAP GoingLive services, which include SAP GoingLive Check. Here, Quick Sizer entries and sizing results are checked against the performance capacities of the hardware you’ve purchased.
Additionally, you can refer a trusted hardware vendor to your Quick Sizer results by giving them your project name and customer number. Your vendor can then view your results to gauge which of their hardware offerings will best fit your needs. Conclusion At a time when every IT project is under increased scrutiny and careful spending is an absolute must, Quick Sizer provides an easy way to ensure cost-effective hardware sizing.
It also lets you work with your hardware vendor to arrive at a properly sized hardware landscape that best fits your needs. We strongly recommend that you get familiar with this tool before your next hardware purchase — you’ll save a lot of money, time, and effort. Visit to learn more. Additional Resources. “.
Landscapers charge according to the size of the stump. Expect to pay between $90 and $150 to have a 24-in.-dia. Stump removed. You can rent a gas-powered stump grinder for about $100 to $190 per day, depending on the size of the machine. Therefore, if you only have to remove a stump or two, you'd be better off hiring a pro. However, if you have more than two stumps or plan to share the rental expense with a neighbor, renting is definitely the more economical way to go.
Make certain the rental dealer explains the controls and shows you how to safely operate the machine. Never use a stump grinder without wearing eye and hearing protection. Note that you'll need a vehicle with a trailer hitch to tow the machine, which weighs about 1000 pounds. If that's not possible, most rental dealers will deliver it to your home for an additional fee.
To remove the 30-in.-dia. Red maple stump shown here, we used a Vermeer Model SC252 stump grinder, the same size machine found at most rental dealers. It has a powerful 25-hp engine and 16-in.-dia. Cutting wheel that's studded with 16 forged-steel teeth. This is a loud, powerful machine with a sophisticated hydraulic system, but it's surprisingly simple to operate.
The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components and the data load they put on the network must be taken into account. With the help of SAP Standard Application Benchmark results at, statements can be made as to CPU consumption and memory consumption of particular software components.
For sizing we have identified three different and independent sizing models that have different advantages and disadvantages. The first two, user-based sizing and throughput-based sizing, have been implemented in the Quick Sizer. User-based sizing: We defined three types of active users who work with the system to a different degree. Merely counting the users can be done quite easily. The disadvantage is that this estimation is quite rough as it says very little about the actual throughput these users produce.
Throughput-based sizing: This model is quite thorough because it relies on actual or on actually expected throughput. However, this model relies on a number of assumptions in business terms (e.g. Number of order line items per year) that need to be cross-checked against the individual installation. Customer Performance Test: The according tests are done in a customer system with customer data. The disadvantage is that conducting these tests requires considerable time and money. For further information please refer to the white paper.
Quick Sizer is a web-based tool designed to make the sizing of SAP Applications easier and faster. It has been developed by SAP in close cooperation with all platform partners and is free of cost. With Quick Sizer you can translate business requirements into technical requirements. Simply fill in the online questionnaire, an up-to-date survey that is based on business-oriented figures. The results you obtain can help you select an economically balanced system that matches your company's business goals. This is especially useful for initial budget planning.
The term “greenfield sizing” is mostly used in the context of new implementations without or with only little experience with SAP software. It refers to the process of finding out what the main load drivers are and attaching some sizing value to them. Very often, this is done in the early phases of a project where actual business processes and required data volumes are not available in detail. So greenfield has two meanings: new to SAP and/or early in the project.
In greenfield sizing, standard tools, such as Quick Sizer and are used. Calculates CPU, memory, disk, and I/O resources based on throughput and number of concurrently active users. For an introduction to Quick Sizer. Complete the following steps:. Access the Quick Sizer tool - use the SAP HANA version if you want to size an SAP HANA database, or the classic version if you want to size a non-SAP HANA database. Create a sizing project - input your customer scenario data into Quick Sizer and it will display the results.
Check for sample configurations - find the appropriate hardware configuration(s) on or on the. Provide the project name to your hardware vendor, who will then propose an appropriate hardware configuration.
If you are unable to find the right sizing for your SAP product in the Quick Sizer tool, consult the sizing guidelines. There are different approaches for productive sizing, depending on the stage of a solution’s lifecycle. The term productive sizing has different meanings. It can be an upgrade-, delta-, re- or migration sizing. To conduct an upgrade-, delta-, re-sizing you typically measure your current resource consumption (i.e., CPU utilization, table growth, and memory usage) to predict future resource requirements.
After analyzing your system, you then add the extra load caused by additional users or new applications. Typically, in an expert sizing, more profound analyses are performed. Very often, this means exploring some business processes in more detail, both on functional and technical level.
There are no standard tools available to conduct expert sizing. There are very different use cases when an expert sizing is required. In most of the cases, an expert sizing is not trivial and requires a lot of SAP expertise. Please refer to this to get a first impression what expert sizing can include.
At SAP, expert sizings are typically covered by Consulting and / or Support. Please check this for additional information.
Purpose The purpose of this page is to guide on how to use the Quick Sizer tool to calculate CPU, disk, memory and I/O resource for your SAP BusinessObjects Business Intelligence Platform 4.0 (BI4.0) system. Overview The Quick Sizer calculates CPU, disk, memory and I/O resource categories based on throughput numbers, and the number of users working with the different SAP Business Suite components in a hardware and database independent format. The purpose of the tool is to give customers and prospects an idea about the size of the system necessary to run the proposed workload. This is especially useful for initial budget planning.
Error codes and the Reference manual can also be included.
This manual includes a description of the functions and capabilities and presents instructions as step-by-step procedures. This document contains important information to use and/or repair your appliance. Depending on the nature of the manual (use, installation, service, parts list), it provides instructions that you can't ignore. We provide PDF manuals: easy to download, the documents can be displayed on any equipment like mobile, tablet and computer.
![Mistral chocolate fountain instruction manual Mistral chocolate fountain instruction manual](http://www.comparestoreprices.co.uk/images/unbranded/i/unbranded-indulgence-by-mistral-chocolate-fountain.jpg)
The Quick Sizer calculates CPU, disk, memory and I/O resource categories based on throughput numbers, and the number of users working with the different SAP Business Suite components in a hardware and database independent format. The purpose of the tool is to give customers and prospects an idea about the size of the system necessary to run the proposed workload. This is especially useful for initial budget planning. Steps to launch Quick Sizer Tool. Go to.
Click Start Quick Sizer. The Quick Sizer window will be displayed. Steps to create a BI4.0 project. Enter values in Customer no. And Project Name, then click Create Project. On left side, under Tree of Elements.
Expand SAP BusinessObjects Portfolio SAP BusinessObjects Business Intelligence, then click the lowest SAP BusinessObjects Business Intelligence. On the right side, click Save button to save your project first. Input the values in the right side table. After finishing the input, click Calculate result button on the top menu bar to run the calculation. The result will be displayed on the bottom-right of the page.
You can change your project anytime by going back to the start page of Quick Sizer, entering your project name and clicking Chang Project. For an example BI4.0 project, enter 'BOBIV26 F.' In Project Name and click Display Project. Related Content Related Documents Related Notes SAP Knowledge Base Article - How to use the Quick Sizer tool to calculate CPU, disk, memory and I/O resource for your BI4.0 environment SAP Knowledge Base Article - How do you obtain the information required by the SAP BI Platform 4.0 Quick Sizer tool? SAP Knowledge Base Article - How to find Sizing information for SAP Business Objects Products.