kamagra how much to take

Estimating Peak Throughput

When users browse, search, check out documents, or select from a list of choices, this usually causes the display of a new page (screen) of information. The more complex functions, such as document management, are especially resource-intensive and may initiate the display of multiple Web pages of information. In general, one user function is approximately equivalent to the display of one new HTTP page on the user’s desktop. Therefore, throughput measurement is based on the premise that HTTP pages per second roughly equates to calculated operations per second.
 
The following list provides key sizing metrics, along with typical values as a guideline:
 
a.  Number of users: The number of potential users (or subscribers) with access to the portal.
 
b.  Percent of active users per day: The percentage of the users who might access the portal during the day. This is typically between 10 percent and 50 percent. This is an important number and one that is usually a point of contention. Most customers like to think that each user hits the corporate or divisional portal each day, but our data indicates otherwise.
 
c.  Operations per user per day: Accesses to the portal home page, searches, category browses, document retrievals, media viewing and so on. Depending upon the user’s role (reader, author, reviewer, or contributor), this will usually range between 1 and 10 operations per day.
 
d.  Hours per day: Hours in the business day. Portal site access can cross time zones; so 10 hours per day might be a typical number for a company spanning the United States.
 
e.  Peak factor: A ratio of how much the peak usage exceeds the average usage. You should size the systems for peak usage so that performance does not degrade during busy periods. A typical ratio is 5:1.  This takes into account that peaks may occur at certain times of the day, such as start of the business day when many users use the system all at once.

 

Characteristic            
Value
a. Number of potential users
TBD
b. Percent of active users per day
TBD
c. Number of operations per active user per day
TBD
d. Number of hours per day
TBD
e. Peak factor
TBD

 

Number of users (a.)
×
Percent of active users per day (b.)
×
Number of operations per active user per day (c.)
×
Peak factor (e.)
TBD ×  Number of hours per day (d.)
 General Metrics
Deployment Scenario
Users
Performance
Single Server Process
< 10,000
20 Web pages per second
Process two search queries per second
Index five documents per second
Store up to 100,000 documents (SQL Server)
Include more than 1 million documents in indexes
Host up to 10,000 team and personal sites
Small Farm
< 25,000
Process 37 Web pages per second (including 5 searches per second)
Index five documents per second
Store more than 100,000 documents
Index 1 million documents
Host more than 10,000 team and personal sites
Host up to 5 portal sites using shared services
Medium Farm
< 100,000
Process 80 Web pages per second (including 12 searches per second)
Index 10 documents per second
Store up to 1,000,000 documents
Index up to 5 million documents
Host more than 10,000 team and personal sites
Host up to 25 portal sites not using shared services
Host up to 10 portal sites not using shared services
Large Farm
> 100,000
Process 100 Web pages per second (including 15 searches per second)
Index 10 documents per second
Store up to 1,000,000 documents
Index up to 5 million documents
Host 50,000+ team and personal sites
Host up to 25 portal sites not using shared services
Host up to 10 portal sites not using shared services
Share

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>