|
Socoder -> Site & Server -> Server Stress!! |
|
| Wed, 20 Sep 2017, 10:33 | |
HoboBen
|
Is that server stress graph the code rewrite or just being too popular? 
-=-=- blog | work | code | more code |
| Wed, 20 Sep 2017, 10:33 | |
Jayenkai
|
It’s infinitely less stress than it was, this time last year! > Reveal 🔎 Overall it's about 1/3rd of the cpu time per page than the total was with the old site's scripts. Time is multiplied.. .. 1000 is 0.1seconds! -=-=- ''Load, Next List!'' 
|
| Wed, 20 Sep 2017, 12:12 | |
|
GfK |
is this something to do with the site being down earlier today? Something about the site's allowance reaching its limit?
|
| Wed, 20 Sep 2017, 12:17 | |
|
Jayenkai
|
It’s nothing to panic about!! Even the highest spikes, there, are still only 0.3 seconds. It’s all nice and healthy! The red line at the bottom is my new AGameAWeek script, averaging 0.05 secs per pageload. The previous Wordpress site averaged about 0.18 per page, or thereabouts, and old SoCoder was usually about the same, if not more. It’s actually a massive improvement over what the site used to run at. -=-=- ''Load, Next List!''
|
| Wed, 20 Sep 2017, 12:18 | |
|
GfK |
...which is amazing, considering the relative cost.
|
| Wed, 20 Sep 2017, 12:21 | |
|
Jayenkai
|
The "server stress" graph can be viewed in real-time, here. For those interested.
-=-=- ''Load, Next List!''
|
| Thu, 28 Sep 2017, 09:11 | |
waroffice
|
Thats cool, you make that your self Jay?
|
| Thu, 28 Sep 2017, 09:18 | |
|
Jayenkai
|
Yep. Everything's now notepad-coded, except for CBParser being the origins of the BBCode. (See link, bottom right.) Although there isn't much left of CBParser, nowadays. The original was jam packed with security holes, which MisterX helped plug up. (Shows how long that's been there!!) -=-=- ''Load, Next List!''
|
| Sat, 30 Sep 2017, 06:26 | |
|
Jayenkai
|
Top users for today, so far. Semrush bot continues to misbehave, even with .htaccess blocking and denial in robots.txt Various forums seem to suggest it takes about 3 weeks before it bothers to notice the change in robots.txt, which is frankly fucked up, given the amount of pages it reads every fucking day. I've tweaked the .htaccess so that everything requested by Semrush bot gets sent directly to the robots.txt file. This means that.. A) the bot will continue to get supplied with content, even if it's all the same robots.txt page, over and over and over.. and.. B) When it DOES eventually bother to request a robots.txt file, then it's damn well going to get one! For kicks, the month's daily clicks. (Although today's not over, but you'll cope!!) 
-=-=- ''Load, Next List!''
|
| Mon, 02 Oct 2017, 09:59 | |
|
Jayenkai
|
Fighting Robots!!!
-=-=- ''Load, Next List!''
|
| Wed, 04 Oct 2017, 06:42 | |
|
Jayenkai
|
 Continuing my quest to quench the server of all evils, today I stumbled upon this sort of behaviour. Not sure what's going on there, but seems to be a botnet of sorts, trying to find a hole in the server. Have blocked "Firefox/40.1" which should hopefully do the trick. Judging from this person's findings I can see that whoever created this particular botnet hasn't bothered to update the thing in over a year, so the 40.1-Block should hopefully do the job I need it to do. Apologies to anyone who actually DOES use Firefox 40.1, but you're gonna get blocked!! -=-=- ''Load, Next List!''
|
| Thu, 05 Oct 2017, 05:16 | |
cyangames
|
SEM Rush are meant to be quite a big player in the SEO world, not impressed by their response. Or their bot.
-=-=- Web / Game Dev, occasionally finishes off coding games also! |
| Sat, 07 Oct 2017, 15:12 | |
|
Jayenkai
|
You'll be happy to know, Semrush has now fucked off!!! Current Top-10 I've dumped most of those bots into the Robots.txt, and we'll see in a few days whether they bother to use that. Cleaner and cleaner!! -=-=- ''Load, Next List!''
|
| Sat, 07 Oct 2017, 15:57 | |
|
GfK |
I was told years back... can't remember who, that robots.txt is only a set of instructions for well-behaved bots - they don't *have* to take any notice of what's in there. More to the point, a rogue bot can actually use the information in there to find exactly the shit you don't want them looking at. Dunno if this is still, or was ever, correct. |
| Sat, 07 Oct 2017, 16:21 | |
|
Jayenkai
|
Yeah, bots aren't legally required to do as the file says. But when a "Good robot, honest"'s accompanying website says "We do, after 3 weeks", and that same bot grabs over 9,000 pages EVERY DAY, then you know that's not exactly being a good robot. It's gone now. On to the others!!!! -=-=- ''Load, Next List!''
|
| Mon, 09 Oct 2017, 08:20 | |
|
Jayenkai
|
 "Curious Botnet" (as I've decided to title it) certainly didn't like being blocked! I've got about 8 hours of similar stats, as the botnet desperately tries to figure out where the none-existent "wp-login.php" suddenly didn't disappear to. Bloody thing. It calmed down, afterwards, and is now doing it's usual "Every 40 minutes or so" scans that it used to do, but blimey that was certainly an unexpected hissy fit that it threw!! -=-=- ''Load, Next List!''
|
| Mon, 09 Oct 2017, 10:15 | |
|
GfK |
Maybe have most of the content invisible to anyone who isn't logged in? That'd fuck with their tiny electronic minds!
|
| Wed, 11 Oct 2017, 05:41 | |
|
Jayenkai
|
 Getting much neater in the stats, now! Most of the bots have cleared off, and the "actual users as far as I can tell" is remaining at a nice approximate level. Now I just need to make something amazingly awesome that generates a bazillion actual users!!! ... ..... Hmmpf -=-=- ''Load, Next List!''
|
| Tue, 08 May 2018, 04:23 | |
|
Jayenkai
|
Been a few months since I had to add a new bot to the robots/htaccess, but hurray, we've got a winner!! Yesterday's Top 10 "Most frequent UserAgent" stats.. FFS!!!! *blocked* -=-=- ''Load, Next List!''
|
|
|
| |||||
|
| ||||||
