Number of concurrent users – The number of concurrent users is the second most important sizing factor. Time and expense entries usually show peaks once per week, whereas Sales order entries often come in bulk via integration or trickle in during the day. ![]() This mostly depends on the transaction type. Transactions – Typically transactions have certain peaks throughout the day/week. If there are multiple peak periods, then these periods need to be accurately defined.Īs you understand the load that impacts your infrastructure, you also need to understand more detail about these factors: ![]() It's important to always find the peak transactional volume per hour. Viewed from left to right, the first and most important factor needed to accurately estimate sizing is a transaction profile or a transaction characterization. The absolute minimum requirement for necessary data is the peak transaction line load per hour. ![]() ![]() Hardware sizing, without supporting data, is likely to be inaccurate. The more detailed information that is collected, the more precisely you can determine sizing. Factors that affect sizingĪll the factors shown in the following illustration contribute to sizing. Pay close attention to the system setup best practices for optimum performance.Īfter you have reviewed the documentation, you can start the process of estimating your transactional and concurrent user volume and sizing your environment based on the average core throughput.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |