Posted on 07/28/2017 9:04:14 PM PDT by EarlyBird
This site fricking sucks.
If you want me to continue to be a member, you will fix it.
So who is for giving Democrats more hugs??
The DOS Denial-Of-Service may decrease if you hug a Democrat today. Democrats are hostile creatures.
If you cannot lower yourself to hug a Democrat, try to say something nice about a Democrat, so they attack FR less.
Something nice like a Democrat’s IQ is higher than a dog’s IQ, if the dog is not sick as a dog.
I believe that if you decline the invite later, and go to another website, you’ll find content and compadres that the left doesn’t object to as much as they HATE FR. Personally, I prefer the content and the clientele that infuriates the left the most. Voila. I appreciate the Robinsons and believe that their efforts to share information have ultimately impacted politics enough to attract DDOS. Prayers up for the Robinsons and what they have done and still do for our country.
On your link, 1 min and 50 second mark.
On my link, 3:00 minute mark. C’mon man, that’s quality beesquit right there.
https://www.youtube.com/watch?v=XhAdzzYSKfY
He`s right. This site sucks. Pages don’t load. It ain`t what it used to be. And the number of whack jobs posting on here is unbelievable. And I am tired of hearing how great the pope is and how much Martin Luther is burning in hell. Clean up the postings and stop allowing whack job liberals to poison this site and maybe many of your problems will disappear.
I am evangelical Christian and haven’t read about how great the pope is and that Martin Luther is toasting in Hades because I don’t read those posts.
I don’t have to read posts by whack job liberals - I skip over those. Don’t see how confronting any of that will keep DDOS away.
perhaps you missed my post hwerre is stated that I shouldn’t have said what i did-
nginx.org is hosted in the Netherlands.
However, the creator of nginx is Igor Vladimirovich Sysoev, for sure a citizen of the former(?) Evil Empire, having been born in Kazakhstan 46 years ago.
That noted, the open-source nginx is probably the best server to place between the internet and one's web content. In market share, nginx currently stands at #2, below Apache, which is an unnecessarily complex Java dog's breakfast. Here is a chart from Netcraft (the green line is nginx, which has just overtaken "Other"):
When using nginx to serve a dynamic site such as FR, you have basically three layers (I know nothing of how FR actually works, just talking in general): the front end (nginx), the back end (the FR server proper, which stitches the pages together from posts retrieved from the database), and the database itself. Between the FR server and the database, there's probably a cache as well (if a page hasn't changed since the last time it was served, then serve the cache copy and avoid the database manipulation delay).
The trick is to let nginx do whatever it can (internet-facing plumbing, serving static assets, such as micky-mouse images) and route only what's necessary to the FR server.
Would be a good idea to put each forum on a separate VM and forgo global searches.
Also, would be a good idea to give signed-on users priority access.
Regardless, I’m happy to go with the flow — fast or slow...
Likewise. It was the late eighties. I was a mainframe jockey, when I latched onto a TI Silent 700, which was an acoustically coupled modem (300 baud) married to a thermal printer / keyboard. It was amazing. One BBS lead to another. Until you ran out of thermal paper.
You dialed the number and stuck the handset into the rubber cups (Mommy, what's a handset?).
It does sort of work like that, actually.
My gut instinct would be to work off the thread ID (the seven-digit number in the post's URL).
E.g., a pool of FR servers, say one or two per available CPU core.
There would be a front end that would search the cache using the thread ID. If found, serve the cache copy. Done. (Presumably, the number of requests for current thread pages considerably exceeds the rate of requests to update threads.)
Otherwise, add the request to a queue of requests for an available FR server.
Hopefully soon, an idle FR server will pick the request off the queue, construct the page from database query results, serve it, and add it to (or replace it in) the cache.
That architecture would push the load back onto the database server. I would use a decent DB, such as PostgreSQL.
That seems like a reasonable starting point for scaling. Thereafter, one would observe the system's behavior under load and take steps to relieve bottlenecks as they occur.
Curious why you are not very late for Freeper breakfast.
It is OK, I love puzzles and stuff.
All you’ll ever want to know about it and lots more here:
DOS - Denial-of-service attack
https://en.wikipedia.org/wiki/Denial-of-service_attack
One thing's for certain. You're making a member outta yerself now!
Oh, put a damn sock in it and knock that crap off.
There's a lot of us long-time FReepers who love this place but are getting endlessly frustrated with the constant slowdowns and outages that haven't been remedied despite our financial contributions.
And, no, I'm not buying a DOS attack. That's BS.
Just FYI, upthread I gave you the link for the original “nginx”, but there is a commercial version with the HQ in S.F....and a secondary offices in Moscow and Ireland:
Thanks for the info.!
Donate $10,000 for new systems, it could help.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.