Also remove the "sleep_for_one_second()" type of function, that usually helps :-D 

Lots of memory and CPU available is the weird part ... Must be IO bound somehow.

You're right though, if I had some decent tracing I could probably figure out what the problem is pretty fast. Working on this now actually. 

k00b

247bf84fda

Yea, hard to armchair debug from here, but I wish I could help :D More logging of timestamps will help...

I see most ajax requests taking over a second. I'm guessing you have a really high qps on the graphql endpoint? It could be memory/cpu bound too?

I had a weird behavior after cleaning cache in Chrome and cold loading stacker.news, then it took 30+ seconds to open the homepage. Not sure what it was stuck on, but the (mainly js files) requests are either "stalled" or "queued".

Daily discussion thread

saloon

Yea, hard to armchair debug from here, but I wish I could help :D More logging of timestamps will help... 

I see most ajax requests taking over a second. I'm guessing you have a really high qps on the graphql endpoint? It could be memory/cpu bound too? 

I had a weird behavior after cleaning cache in Chrome and cold loading stacker.news, then it took 30+ seconds to open the homepage. Not sure what it was stuck on, but the (mainly js files) requests are either "stalled" or "queued". 