Stories
Slash Boxes
Comments

SoylentNews is people

Meta
posted by on Sunday October 30 2016, @02:45PM   Printer-friendly
from the no-fishing-for-me-this-morning dept.

Right, so there's currently a DDoS of our site specifically happening. Part of me is mildly annoyed, part of me is proud that we're worth DDoS-ing now. Since it's only slowing us down a bit and not actually shutting us down, I'm half tempted to just let them run their botnet time out. I suppose we should tweak the firewall a bit though. Sigh, I hate working on weekends.

Update: Okay, that appears to have mitigated it; the site's functional at a reasonable rate of responsiveness.

Update2: Attack's over for now. You may go about your business.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Monday October 31 2016, @12:02AM

    by Anonymous Coward on Monday October 31 2016, @12:02AM (#420714)

    Ah the 'its pure' design. Well yeah it is readable. But runs like crap.

    It usually takes a mess like that to teach someone that 'yeah 50 round trip calls across the network are not good'. Cache it and aggregate it.

    With one system I worked on a stored proc was digging through the same LARGE table 15 times to get different columns. One bit of caching it into a temp table and moving stuff around it went from 1.5 million reads to about 12 reads.

  • (Score: 2) by NCommander on Monday October 31 2016, @04:48AM

    by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Monday October 31 2016, @04:48AM (#420783) Homepage Journal

    Honestly, you can get both without having a ton of crap as your codebase. Build an interface to do what you want, then slide a caching layer below it. If you've done it right, you get the best of both worlds. While not completely invisible, if you're using caching sanely, and know exactly how it operates, you can drastically reduce cache misses while rarely having to explicately code around the problem of dirty reads (MySQL cluster handles this for us). Rehash's core basically is proof; it's not the most brilliant pile of Perl ever written, but CmdrTaco actually knew what he was doing from a software development perspective. Most of the garbage we stripped out were later additions that were basically tacked on.

    --
    Still always moving