RSS feed readers are BACK, babe!
-
Really? Its pretty fast for me rn.
@irelephant @cwebber when i click the ⋯ next to this post, then click "open original page", and i start a stopwatch the moment i see the new tab open, i see:
- a picture of a bug and a sentence of text.
- the sentence of text is replaced with "did you know nachos aren't even mexican".
- a skeleton of the wafrn layout, and a throbber.
- eventually, the post.Final time on stopwatch: 2.26 seconds.
I do the same thing on a cosocial post: https://cosocial.ca/@evan/115220440152189152
Result: Under 0.5 seconds.
-
@irelephant @cwebber when i click the ⋯ next to this post, then click "open original page", and i start a stopwatch the moment i see the new tab open, i see:
- a picture of a bug and a sentence of text.
- the sentence of text is replaced with "did you know nachos aren't even mexican".
- a skeleton of the wafrn layout, and a throbber.
- eventually, the post.Final time on stopwatch: 2.26 seconds.
I do the same thing on a cosocial post: https://cosocial.ca/@evan/115220440152189152
Result: Under 0.5 seconds.
@irelephant @cwebber The cosocial page loaded so fast I actually couldn't successfully stopwatch it.
-
@irelephant @cwebber The cosocial page loaded so fast I actually couldn't successfully stopwatch it.
2 seconds for the initial load when there is a PWA update is not bad.
#I-consider-it-an-acceptable-time #reducing-that-would-make-the-server-go-from-18€-to-81 -
2 seconds for the initial load when there is a PWA update is not bad.
#I-consider-it-an-acceptable-time #reducing-that-would-make-the-server-go-from-18€-to-81gabboman@app.wafrn.net mm using PWA as an excuse to hand wave away slow page loads is so 2010s
NodeBB is a PWA and loads plenty fast, although there is a server side rendering component there.
-
fair enough. No im seeing some issues on network side on the initial load at times. But still, 2 seconds is quite ok for the target im going for
#i-admit-is-going-slower-than-usual-today-tho -
it is my fault because its my code haha
-
Yeah but I'm saying all the endpoints are laggy, which is more likely just a server bottleneck, which is due to the plan you are subscribed to, and less so your own code
Oh no! I just did an update
It was regarding of separating fedi and “user actions” in two threads -
This one was more of node event loop having too many events. I dont know if it was placebo or not
-
She's specifically looking at the time it takes to view single posts - not using wafrn as an app from a user's perspective. I feel like I'd agree that 2+ seconds to load a view of a single text post is quite long by most standards, whereas it's less of a big deal for loading a dashboard you're going to be spending a long time on.
-
She's specifically looking at the time it takes to view single posts - not using wafrn as an app from a user's perspective. I feel like I'd agree that 2+ seconds to load a view of a single text post is quite long by most standards, whereas it's less of a big deal for loading a dashboard you're going to be spending a long time on.
After further investigation we did some changes and performance on an user level is a lot better. Still arround 2 seconds for threads. But better on actions
#Js-event-loop-has-its-limits
