[HN Gopher] Server is smoking, trying to figure out why
       ___________________________________________________________________
        
       Server is smoking, trying to figure out why
        
       Author : diogenesjunior
       Score  : 110 points
       Date   : 2021-06-07 20:31 UTC (2 hours ago)
        
 (HTM) web link (twitter.com)
 (TXT) w3m dump (twitter.com)
        
       | seryoiupfurds wrote:
       | > Something went wrong. Try reloading.
       | 
       | Seems like Twitter isn't doing much better.
        
       | vlmutolo wrote:
       | Was the last outage really in 2015
        
       | jpeter wrote:
       | I thought Replit started ddosing the site
        
       | ballenf wrote:
       | I really thought it was going to be someone complaining about
       | their restaurant server having a smoke break. Thought it must
       | have been covid related to make the front page. But don't ask me
       | how.
        
       | phendrenad2 wrote:
       | "Smoking" meaning running high CPU, presumably, not literally
       | smoldering
        
       | bombcar wrote:
       | I had an older Dell give up the magic smoke recently and
       | literally - https://i.imgur.com/WHYODQS.jpeg
       | 
       | Amusingly enough I smelled it weeks ago and it finally shut off a
       | few days ago.
        
       | oxfordmale wrote:
       | Did you try nicotine patches?
        
         | loves_mangoes wrote:
         | ...nicotine? =)
        
       | el_benhameen wrote:
       | If it's any consolation, I thought my wireless provider had
       | booted me before I realized HN could be having issues. It's
       | generally so fast and reliable that I use it as my "is my
       | internet broken?" sanity check page.
        
         | lapp0 wrote:
         | Ahahah, similar situation here. I thought maybe our IT
         | department had noticed my activity here and decided to throttle
         | my connection (which would still be an odd solution instead of
         | just outright blocking it), but still it took me a few minutes
         | to suspect that maybe the problem was with HN itself.
        
           | whoisburbansky wrote:
           | Also assumed this, was only convinced otherwise when I ran
           | into the same issue on my personal mobile phone, on a data
           | network separate from my work network.
        
         | masswerk wrote:
         | Same here. :-)
        
       | bilalq wrote:
       | I interpreted this much more literally. When the updated tweet
       | about a code revert fixing it came out, it took me a second to
       | figure out what was meant.
        
         | AceJohnny2 wrote:
         | https://en.wikipedia.org/wiki/Halt_and_Catch_Fire_(computing...
        
       | nomoreplease wrote:
       | Update provided
       | 
       | > Welp, figured out why - because I am idiot. Routine code change
       | exploded performance. Only took me 2 hours to think of reverting
       | it. Sorry!
       | 
       | https://mobile.twitter.com/HNStatus/status/14020112741043609...
        
         | bryan_w wrote:
         | If they are reading this and need an SRE to help out let me
         | know. We are really good at reverting the shit out of an
         | release when it breaks prod.
        
         | MontyCarloHall wrote:
         | Besides applying security patches, what exactly has needed to
         | be changed in the HN codebase over the last 14 years?
         | Featurewise, it's been essentially static for its whole
         | existence (which is a large part of its appeal to many,
         | including myself).
        
           | xeromal wrote:
           | If the number of users has grown over the last 14 years, I'm
           | sure some of the code areas have needed to be tuned over 14
           | years as well.
        
           | AnotherGoodName wrote:
           | When you hit scale every edge case becomes a reality.
        
           | jolmg wrote:
           | I think I've noticed changes a few times. For example,
           | 
           | - the relative timestamps would go up to days, so you'd see
           | e.g. "3121 days ago", and now they're replaced with dates at
           | some point.
           | 
           | - we're now able to escape * in comments
           | 
           | - code blocks no longer scroll horizontally and wrap instead
           | (my favorite change because many code blocks were actually
           | bullet paragraphs)
           | 
           | - the "past" link in the navbar was added
           | 
           | - the subthread collapse link [-] used to use a - (ASCII
           | 0x2d) and now it uses - (Unicode U+2013). This is my least
           | favorite change because I used to use that for keyboard
           | navigation. It was pretty convenient to Ctrl+F [- <Enter>...
           | to navigate between comments then <Esc> <Enter> to collapse a
           | thread and Ctrl+F <Enter>... to keep navigating.
           | 
           | These are pretty recent changes.
        
             | viraptor wrote:
             | There's also the "second chance" list (few months ago?)
        
       | jensenbox wrote:
       | Nicotine is a hell of a drug.
        
       | Hublium wrote:
       | > It's a difficult habit to quit
       | 
       | LOL
        
       | raverbashing wrote:
       | If you think about it, it's impressive how such a high traffic
       | site works out using a niche language which what I assume is not
       | such a big ecosystem.
       | 
       | (On the other hand there's moderate complexity but low page sizes
       | and nothing like modern websites with hundreds of cookies, heavy
       | js, etc)
        
       | smegcicle wrote:
       | something about deep comment thread folding?
        
         | 1vuio0pswjnm7 wrote:
         | Yesterday I saw a strange artifact in a comment. Instead of the
         | usual "[-]", I saw "[2 more]". Did not seem right.
        
           | extra88 wrote:
           | That's what it says after you use the [-] to collapse a
           | comment and it has a single reply. It also counts replies to
           | replies (and so on).
        
             | jolmg wrote:
             | Yes, but could it be that it used to show [+] before? or am
             | I misremembering?
        
       ___________________________________________________________________
       (page generated 2021-06-07 23:01 UTC)