Conversation
Notices
-
-
@moonman Mines been mostly fine except for the occasional hiccup when someone decides to try to get around my images patch.
-
@moonman I sense with later versions we're starting to see requirement creep beyond the smaller virtual boxes that many instances are on, though.
-
@maiyannah I tried to load a notice on yours and I sat there for like most of a minute waiting for it to load. It did eventually though.
-
-
@maiyannah I haven't gon directly to your site for a while so it might be a caching thing it's doing.
-
@moonman I get 1.69 seconds load (harharhar) average when I run it through my small battery of speed test sites.
Still a little slow for what it should be but hardly intolerable.-
@maiyannah @moonman I notice it loads fast on Firefox, but Chrome takes a while to load your instance completely.
-
@normandy @moonman Chrome doesn't process asynchronous javascript .. asynchronously, so that's to be expected, whereas IE, and Firefox do.
-
@maiyannah @normandy none of them do unless you're using web workers or service workers. Unless I misunderstand what you're saying. All JS engines are singlethreaded. and can only interrupt a function that has a yield in it.
-
@moonman @normandy I don't mean executing the javascript, I mean loading them. When you flag a javascript to load asynchronously, the browser loads all those javascripts at the same time. If you do not, it loads them sequentially, which increases the load time for the site, obviously (as well as the connection overhead if you aren't using/abusing KEEPALIVE)
-
-
@moonman ./api/statusnet/conversation/72838.json?count=100&_=1465779905037 is the longest load point by far though so the API may be bottlenecking/slowing it down some.
-
-
-
-
-
-
@moonman I haven't noticed any particular problems on mine. I did hear that some instances were moved around today, though.
-
