<html><head><style id="outgoing-font-settings">#response_container_BBPPID{font-family: initial;font-size: initial;color: initial;}</style></head><body style="background-color: rgb(255, 255, 255); background-image: initial; line-height: initial;"><div id="response_container_BBPPID" style="outline:none" dir="auto" contenteditable="false"> <div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"> What I find interesting is how do any of these VPSs find customers? Ionos is yet another company I never heard of. Looks more like hosting than a VPS. You can access the nginx configuration file? </div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%">Policing shared resources is tricky. It is hard to put into a contract the allowed nature of your network traffic other than a cap on transit. But the out a company has is they can just drop you as a client any time they feel like it. You can also be banned. So it pays not to attract bots. </div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%">These VPSs and hosting companies do some traffic shaping. Nothing says they can't in the contract. So the traffic from bots will go into their algorithm. That is why you want to stop the bots and hot linkers. I use nginx to redirect the hot linkers to the index.html. </div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div><div id="BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div> <div id="response_div_spacer_BBPPID" dir="auto" style="width:100%"> <br></div> <div id="blackberry_signature_BBPPID" dir="auto"> <div id="_signaturePlaceholder_BBPPID" dir="auto"></div> </div></div><div id="_original_msg_header_BBPPID" dir="auto"> <table id="_pHCWrapper_BBPPID" width="100%" style="border-spacing:0px;display:table;outline:none" contenteditable="false"><tbody><tr><td colspan="2"> <div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb( 181 , 196 , 223 );padding:3pt 0in 0in;font-family:'tahoma' , 'bb alpha sans' , 'slate pro';font-size:10pt"> <div id="from"><b>From:</b> noloader@gmail.com</div><div id="sent"><b>Sent:</b> February 14, 2022 4:53 PM</div><div id="to"><b>To:</b> nginx@nginx.org</div><div id="reply_to"><b>Reply-to:</b> nginx@nginx.org</div><div id="subject"><b>Subject:</b> Re: Obvious malware rejection module?</div></div></td></tr></tbody></table> <br> </div><div dir="auto" style="outline:none" contenteditable="false"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 14, 2022 at 6:17 PM lists <<a href="mailto:lists@lazygranch.com">lists@lazygranch.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div style="background-color:rgb( 255 , 255 , 255 )"><div id="gmail-m_-5227844091454555428response_container_BBPPID" style="outline:none medium" dir="auto">...<div id="gmail-m_-5227844091454555428BB10_response_div_BBPPID" dir="auto" style="width:100%"><br></div><div id="gmail-m_-5227844091454555428BB10_response_div_BBPPID" dir="auto" style="width:100%">I have plenty of transit capacity. I can serve 3TB a month and I do 30GB. What I don't have is CPU power. I have a one CPU VPS. The CPU is shared resource. I think the RAM used by the VPS is more "available," if that makes any sense. That is they don't swap you out but let your VPS sit in RAM. So something RAM intensive is fine but CPU intensive is not. <br></div></div></div></blockquote><div><br></div><div>Off-topic, we used to use GoDaddy for VPS for our free/open source software project. It was a crummy service offering one virtual core, 1 GB of RAM and no swap file. The VPS ran on a circa-2005 4-core Athlon machine.</div><div><br></div><div>The server had constant problems because the OOM killer would whack our MySQL process. We needed it for a Mediawiki
installation
. The machine could not handle the LAMP stack.<br></div><div><br></div><div>And GoDaddy would send us nastygrams threatening to stop service because of bots. When the spam bots tried to create a new page the wiki server pegged at about 100% cpu for a moment while that new editor was spun-up.</div><div><br></div><div>We now use Ionos (<a href="https://www.ionos.com/hosting/web-hosting">https://www.ionos.com/hosting/web-hosting</a>). The cheapest plan is $1/month. We splurge a bit and pay $5 for the extra core and extra memory. No more OOM problems, and no more nastygrams.<br></div><div><br></div><div>Jeff<br></div></div></div>
</div></body></html>