3 ms·

I noticed it too. I'm not sure what's happening, because that code hasn't changed in a long time.

by pg 17y ago

patio11 17y ago
FWIW: I almost always post in the 7 to 11 AM range Pacific time, and my experience is that one upvote in the first twenty minutes is frequently sufficient for frontpaging at these times on the weekends. I've literally never seen it take more than two, if they're in the first half hour. Edit: changed strength of above writing somewhat. My memory is bad and I don't have contemporaneous records, which should make me wary of saying things like "almost always."
axod 17y ago
Another bug report/oddity: Loading any page when I'm logged in has started taking forever. If logged out, it doesn't take long to load. For example: This comments page loads in 981ms when I'm logged out. If I log in as axod, it loads in 7.5 seconds. Maybe it's just my account :/ Hopefully it's not a 'moderation feature'. Maybe due to a reasonably high comment count for my account? idk but it makes HN pretty boring waiting for page loads. Is anyone else seeing this behavior?
- DanielBMarkham 17y ago
  Wow. Not here, but over the past few months, the app has been consistently fickle about loading up the userinfo page and the threads page. Sometimes it works. Sometimes not. On really high-load days, it was taking 7-15 seconds and then just stopping to show the page. Paul said a week or two ago (I think) that he was tweaking the GC because of the load on the box. Not sure if that could be a factor or not.
  - pasbesoin 17y ago
    I've noticed a difference since he announced the changes to GC. There is perhaps more frequently a noticable delay, but the delay is shorter and eventual page load much more reliable -- I seldom experience a timeout / blank screen, now. Formerly, things would tend to load either almost instantaneously or not at all. E.g. comment pages. Now, there is not infrequently a second or three's delay, but then the page does indeed appear. I find this much more preferable.
    - pasbesoin 17y ago
      Sorry for the initial duplicate posting of the parent. When I clicked the button "Reply", I was redirected to: http://news.ycombinator.com/threads?id=pg http://news.ycombinator.com/threads?id=pg instead of back to this comments thread. Thinking I'd hit a glitch, I backed up and tried again. So, I did hit a glitch in the redirection, but after my comment was processed and accepted.
      - starkfist 17y ago
        Just wanted to chime in and say that I've seen behavior like this a few times. After submitting a comment, I've been redirected to someone else's threads?id page.
  - deleted 17y ago
    [deleted]
cperciva 17y ago
This is wild speculation, but... is it possible that this is related to caching? My understanding is that the ranking of front-page items is based on [# points]/[time since submission], which is obviously very large immediately after an article is submitted; this wouldn't normally matter much, but if the high points/time value is being cached, a low-point submission could stick around on the front page until the cache entry expires.

I noticed it too. I'm not sure what's happening, because that code hasn't changed in a long time.

by pg 17y ago

I noticed it too. I'm not sure what's happening, because that code hasn't changed in a long time.

FWIW: I almost always post in the 7 to 11 AM range Pacific time, and my experience is that one upvote in the first twenty minutes is frequently sufficient for frontpaging at these times on the weekends. I've literally never seen it take more than two, if they're in the first half hour. Edit: changed strength of above writing somewhat. My memory is bad and I don't have contemporaneous records, which should make me wary of saying things like "almost always."

axod 17y ago

Another bug report/oddity: Loading any page when I'm logged in has started taking forever. If logged out, it doesn't take long to load. For example: This comments page loads in 981ms when I'm logged out. If I log in as axod, it loads in 7.5 seconds. Maybe it's just my account :/ Hopefully it's not a 'moderation feature'. Maybe due to a reasonably high comment count for my account? idk but it makes HN pretty boring waiting for page loads. Is anyone else seeing this behavior?

DanielBMarkham 17y ago
Wow. Not here, but over the past few months, the app has been consistently fickle about loading up the userinfo page and the threads page. Sometimes it works. Sometimes not. On really high-load days, it was taking 7-15 seconds and then just stopping to show the page. Paul said a week or two ago (I think) that he was tweaking the GC because of the load on the box. Not sure if that could be a factor or not.
- pasbesoin 17y ago
  I've noticed a difference since he announced the changes to GC. There is perhaps more frequently a noticable delay, but the delay is shorter and eventual page load much more reliable -- I seldom experience a timeout / blank screen, now. Formerly, things would tend to load either almost instantaneously or not at all. E.g. comment pages. Now, there is not infrequently a second or three's delay, but then the page does indeed appear. I find this much more preferable.
  - pasbesoin 17y ago
    Sorry for the initial duplicate posting of the parent. When I clicked the button "Reply", I was redirected to: http://news.ycombinator.com/threads?id=pg http://news.ycombinator.com/threads?id=pg instead of back to this comments thread. Thinking I'd hit a glitch, I backed up and tried again. So, I did hit a glitch in the redirection, but after my comment was processed and accepted.
    - starkfist 17y ago
      Just wanted to chime in and say that I've seen behavior like this a few times. After submitting a comment, I've been redirected to someone else's threads?id page.
- deleted 17y ago
  [deleted]

cperciva 17y ago

This is wild speculation, but... is it possible that this is related to caching? My understanding is that the ranking of front-page items is based on [# points]/[time since submission], which is obviously very large immediately after an article is submitted; this wouldn't normally matter much, but if the high points/time value is being cached, a low-point submission could stick around on the front page until the cache entry expires.