A data warehouse reporting test (2)

1. Background

The project will test recently finally over, before written an article, written by problems encountered during testing, interested students can go have a look at the article.

2. The purpose

      After the project problems have not been fundamentally resolved. Pedigree triggered a series of thinking, and today we want to talk.

3. Thinking Caused

     The previous article wrote was a problem of pressure measurement reporting system, the question of shifting a vendor, vendor staff to do two on-site support, but the results are unsatisfactory. Asked the deep underlying principles of their products, why would lead to the recovery of memory, the system reports "unavailable phenomenon", however. . . . . .

     In Tucao here, sent to support the people, how to minimize the Remote Desktop (TM) are not clear, I was drunk.

Thinking 1: script uses an anonymous logon to query reports.

    ip value-added white list to explain here the anonymous login, in fact, a white list, the machine will execute the script, and then the token can be obtained by specifying the url, let's use this token to access the specified report. This avoids the steps of logging into the system. (Because they themselves did not solve the problem login password encryption system, it was also chat with them to provide the encryption password is not, however respond but it is now also used to test themselves anonymous landing approach).

    This script is extremely simple, send a request to obtain token, and then send a request (with token) to view the report, this approach is reasonable? Imagine a real environment the user is what this scene? Obviously not. . . . . Imagine such a way as compared with the script under genuine LR record is not out quite a few page requests will be less?

Reflection 2: Ignore think time this pressure measured way in the end there is no problem

   Once again one pressure measurement issues before the articles mentioned in the test. Ignore think time in this way using pressure measurement, pressure measurement reporting system will be a long time before the articles mentioned in the question. Here again comes to OLTP, OLAP

What is OLAP: Online Analytical Processing

What is OLTP: Online Transaction Processing

   Our common interface pressure measurement (say range again on some of the usual add, delete, change, check) belong to OLTP, OLAP however, is the main application of the general data warehouse system for analyzing large amounts of data OLTP formed, saying that white is these historical data analysis and processing, more read operations.

   The last solution is to increase the pacing value, 3s, 4s, 5s were carried out to try. In fact, on script before weakening (from the perspective of initiating pressure), which is more close to the real business scenarios. Online users have been less, in fact, far from the kind of query-intensive ignore thinking time. In reality it is impossible to exist in non-stop business people crazy query reports.

  But in the end still want to say next, ignore thinking this way time itself is no problem. Does not fit the current scenario, if there is such a scenario really is, or that I should look at your system performance at a high click-through rate, then it would have this way of.

   Problem again, at such a high click-through rate, pressure measurement for a long time (about 20min), the system has given rise to the phenomenon of unusable in a short time can not restore, you need to manually restart a service product can, this I do not think it is ok phenomenon of. This product requires personnel to root out its causes, is not the product defects.

Guess you like

Origin www.cnblogs.com/jwcz/p/11787973.html