Changes between Version 7 and Version 8 of Ticket #1603, comment 6


Ignore:
Timestamp:
08/06/18 02:54:59 (4 years ago)
Author:
huifeidexingyuner@…

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1603, comment 6

    v7 v8  
    33(1)2000 requests per millisecond, which also mutexes the count(ngx_shmtx_lock), so that if only 1,000 requests are allowed per second, the next 1,000 will be rejected。And the update request count is as follows:
    44   If (now-last)/1000*limit_count is greater than req_count, then req_count=0; otherwise, req_count-(now-last)/1000*limit_count 。   Is that wrong?
    5 (2)Is it because (now-last) time results may be too short,one millisecond of concurrency is too much and this one-second calculation may not work and result in server overload?It doesn't feel like it
     5(2)Is it because (now-last) time results may be too short,one millisecond of concurrency is too much and this one-second calculation may not work and result in server overload?
     6   It doesn't feel like it. If 10,000 requests come in a millisecond, I'll reject the remaining 9,000.
     7