The most scary thing for schools when wireless Portal is online is late peak Carton: students have been connected to WiFi, certification pages are being turned around, or web pages can be closed half a day. The first reaction of the transporter is often that the authentication server is not working.
First tier: authentication server itself
The authentication server carries all requests for entry, at night peaks and high levels, and if the processor or memory runs full, new requests are queued. We usually look at the real-time load curve of the server, with a peak time processing machine that continues to outperform eight accomplishments. This layer is solved by adding servers or clustering, but it must be confirmed whether it is or not, without seeing the card. A school once added three servers or cards, and finally found bottlenecks not at all.
Second tier: backend database
The authentication server checks the account number and writes logs through a database. If the database is not separated, indexes are not well-developed, peak queries slow down, certification requests follow the card. We have seen tens of thousands of entries on the account number list without indexing, and it takes seconds to log in at night. This layer of problems can be seen from end to end detection and application grab bags, not just by looking at servers.
Level 3: Webback
Access points send authentication requests back to the server, which is not sufficiently wide or missing the package. We usually measure the quality of the core to the buildings and the drop rate at night is higher than 1%. Return issues are often misconstrued as server problems because they are all circles.
Level 4: Wireless access points
Access points are limited in their own capacity, a building is too crowded to be used for terminals, the access point processors are full and freshmen are not connected, let alone certified. We have seen schools overloading late peak access points to save money. The certification request is simply impossible. This layer is built on access density and tape planning, not on authentication systems.
Fifth floor: portal page load
The authentication page itself is slow to be recognized as slow when it is opened by the external resources and the pictures are too large. We suggest that the certification page should be a light, cost-effective one, not dependent on the outer web, and that load control should be at the millisecond level. This layer is most easily ignored because people tend to count slowness on servers.
How to get a layered position.
Positioning is measured by a segment: from the terminal to the access point, the access point to the server, the server to the database, and then by section, delays and drops. We usually go up and we bury layers of surveillance, and Carton sees which curves are abnormal when it happens. Blind extension is just a break in money, and layering is the right way.
Cache and Session-maintain pits
The authentication system typically caches login sessions and avoids re-examination of each page. But the cache is too large, the server memory will be eaten; it is too small for students to turn a page and they are kicked back into a chain. We suggest that the session cache should be kept 1.2 times as high at night and with reasonable expiry time. This parameter should be lined up to the real curve without ever having a value.
The pressure is supposed to simulate a true peak.
Many schools do not run pressure before they get online, or use average models, and the peaks fall at night. We suggest that we test the peak model obtained by the touch, and that the hair count, end type, request frequency be real. When you press it, you deliberately fill a layer with how the system downsizes and recovers. The true-pressured system has its bottom in the evening peak; if you don't press it, you can only pray.
The difference between cellular and laptop performance
In the real battle, there is a detail: at the same point of access, mobile phones are slow to authenticate and notebooks fast, or in turn they are often linked to terminal wireless protocols, hibernation mechanisms. We suggest that both types of terminals be covered when pressure and discharge barriers are applied, rather than simply laptops. The behaviour of a student is dominated by cellular phones, which represent a true experience.
Call the police and get in touch with the worksheet.
Carton tells the police to send out only messages, and it is best to send a copy directly to the duty officer to handle the closed loops. We suggest that the alarm and the industrial system link up, who receives the call and deals with it for as long as they can, so that no one can be involved.
The wireless Portal peak, Carton, rarely a single cause, has to be located first on the specific level. Servers, databases, return trips, access points, portal loadings, five layers of pipe-by-pipe corrections. Blind extension is only throwing money into water, so stratification is the right way.