View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004138 | unreal | ircd | public | 2012-10-27 04:54 | 2015-07-13 22:17 |
| Reporter | Assigned To | syzop | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.10-rc1 | ||||
| Summary | 0004138: TKL optimization opportunity | ||||
| Description | When a TKL hits (especially a spamfilter TKL), we should shift the TKL entry towards the list head by a node. This way you have a list of TKLs which are ordered by how likely they are to hit. Also, it may be possible to reduce the set of messages checked by spamfilter by allowing it to only apply to users which have been connected for a specific amount of time. Users which are older than say, 10 minutes, are likely legitimate and don't need to be checked by the filter. | ||||
| 3rd party modules | |||||
|
|
codemastr suggested this 7 or 8 years ago as well, but neither of us implemented it. In normal circumstances it only has limited benefit, it's mostly useful when under attack. Because, 99% of the time (and hopefully more near 99.9%) the spamfilters don't match, then it doesn't matter in which sequence they didn't match. When under attack (high match rate) it would be beneficial though.. so feel free to take a look at implementing this, since under such a peak load it could save substantial CPU... which is right when we need it. I'm not too positive about the other suggestion though ;) |
|
|
not really required. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-10-27 04:54 |
|
New Issue | |
| 2012-10-28 08:40 | syzop | Note Added: 0017210 | |
| 2015-07-13 22:17 | syzop | Note Added: 0018488 | |
| 2015-07-13 22:17 | syzop | Status | new => closed |
| 2015-07-13 22:17 | syzop | Assigned To | => syzop |
| 2015-07-13 22:17 | syzop | Resolution | open => no change required |
