Just confirmed that it's still enabled. The last few days I've found the server starts to get noticeably slower around the 50k bot mark, and the bot number tends to hit about 70k before it starts dropping off again.
XF Bot Guard 1.4.1
- Thread starter zeeb0t
- Start date
I can see it is nearing 75k bots now... and while slower than before, it is still operational. I don't really have a sense of what it was like beforehand. Btw, did you truncate the tables from my prior post? It may help to do that so it doesn't have old visitor data to query / sort through in indexes etc.
True, page loads have noticeably slowed, but it's still an improvement over the last version.
I didn't think about that. I'll run the truncation commands now.
Another thing - when dealing with extremely high bot counts, you may consider disabling:
- Contextual link canaries
- Link Chronology
I don't know if you just truncated, but it all seems pretty snappy again now and it still says about 85k bots.
Yeah I was just gonna say it feels like survival mode just kicked in because page loads just got faster.
Done. (And yeah the truncation was done about 25 minutes ago so it probably wasn't that.)
Last edited:
It might make sense to help survival mode kick in a little longer and sooner, with such bot numbers:
| Option | Default | Recommended |
|---|---|---|
| Enable origin survival mode | Off | On |
| Origin survival mode Retry-After seconds | 60 | 300 |
| Origin pressure database enter threshold (%) | 70 | 50 |
| Origin pressure database exit threshold (%) | 50 | 30 |
| Origin pressure minimum active time (seconds) | 120 | 600 |
| Origin pressure 1-minute load per core % | 300 | 150 |
| Origin pressure CPU busy % | 98 | 90 |
| Origin pressure IO wait % | 30 | 15 |
| Origin pressure swap-out pages per second | 128 | 16 |
| Origin pressure cache duration | 5 | 5 |
Outstanding, I'll give those settings a go.
With those two features off, light-db on, and more proactive survival mode settings, hopefully it won't get to crisis mode even at 80k bots. Although, again no context of before, while it had slowed, it was not to the point of "this website is down" slow. So that's something, IMO. Anyway, bring on the next wave!
Yeah, prior to this update we were still running 1.3.4 and the server would become unusable as soon as it hit above 70k. So I could definitely feel an improvement, although it pretty much just allowed the server to handle more bots before survival mode kicked in, lol.
Thank you for the help! That's one real world test down and hopefully the next one works out even better.
Yeah... I mean, it created a material increase in overall capacity. So, a very decent performance increase. Just a shame there were even more bots ready to eat up those gains.
The next wave will either be overcome, or produce an even higher capacity... I am hopeful its basically a bit of both with those feature and option tweaks.
P.s. you should totally edit the members online phrases for Bot Guard so it reads Clankers: instead of Bots:
How did I not think of that. 
How did I not think of that.
I can see it has entered survival mode. I would say perhaps we should aim for a mid range survival set.
For now, I would just reduce Origin pressure minimum active time (seconds) to 120 and Origin survival mode Retry-After seconds to 60.
They are the defaults for those two. Basically its entering survival mode far earlier - probably not a bad thing as it allows good bots and known members access. But the durations we changed are a bit lengthy. I would just shorten them and enjoy the relative stability for a while.
Will do, thanks.
So have you released new version with light DB?
. I haven't received any notification on that. Anyway, I went through enable cache on my forum, do I need to input anything on the add-on settings ?
All sorted
How's it going for you this time around?
I haven’t checked the database yet. But wanted to ask, when choosing the light DB, what happens to already filled tables in DB?
