ML Performance Issues on Safari
-
@coliver said:
I get near constant lag with Firefox and Chrome, sometimes it can take a minute or more to post comments. Seems to happen at my house too.
Interesting, I do not experience that at all.
-
@JaredBusch said:
@coliver said:
I get near constant lag with Firefox and Chrome, sometimes it can take a minute or more to post comments. Seems to happen at my house too.
Interesting, I do not experience that at all.
Not entirely sure what it is, I've cleared the cache on both machines. I run Windows 8.1 here and at home, but it also effects my Linux Mint laptop (Chrome and Firefox) and my Windows 7 Laptop (IE and Chrome). Just the weirdest thing. I am going on the road in another week for a bit going to try it out at the hotel and NC offices just to check if it is the internet connection.
-
@coliver said:
I get near constant lag with Firefox and Chrome, sometimes it can take a minute or more to post comments. Seems to happen at my house too.
Ditto. I haven't tried moving to IE 11 yet.
-
Just had this happen on my Windows 8.1 desktop in Chrome..
I was on the unread page.
I clicked on the replied XX minutes ago link for the schmooze topic to see the reply.
The page sort of reloaded. The URL change, but the header still showed 2 unread.
The page went white.
While I was highlighting this in Greenshot, the unread page eventually loaded and I clicked on the link again. -
Well that's a new one. I get the blank pages from time to time, but not where I could highlight something in the middle.
-
Not sure if we are seeing code issues, capacity issues or what. Nothing drastic but it could be snappier. We've not had a chance to do a major update yet, so that is coming. And @Minion-Queen has authorized doubling the size of the system, so we are going to be scaling up a bit very soon which should have some serious impact on the performance, I hope. Not that things are slow, much faster than most communities, but we don't want to use that as a bar. We want it to be fast. The faster the pages, the better the interaction, obviously.
Between the two major changes, hopefully we will see some performance gains and fewer of those weird issues.
-
I haven't had any issues in Safari at all. However Chrome and Firefox do that to me all the time (load with nothing there). IE I don't usually use except when on my surface (which I am on now) not seeing anything there.
Hopefully with the scaling about to happen and the updates. Things will get a little better.
-
It is possible that I was experiencing flaky wireless issues.
-
Speaking of mobile access - how do you get to the end of a thread when on the mobile version of ML? There is no link 1 out of 4325 to click on.
-
@Dashrender said:
Speaking of mobile access - how do you get to the end of a thread when on the mobile version of ML? There is no link 1 out of 4325 to click on.
It sucks, that is high on my list of "things I want NodeBB to fix." We need a "go to end" option. There are two ways that I have found...
- Scroll to the bottom of the first page and then select the last page. Argh.
- Post something and it will take you there when it posts.
-
The inability to get to the end of threads is really crappy. It used to work several months ago.
-
I know this is about Safari, but I am getting issues on my Windows Phone's IE (yeah, I know... get a real browser/phone...). Someone else may have the same issue, so I thought I'd add my bit...
There is a huge delay in hitting the submit button and the post being submitted. The button greys out after hitting it, sometimes it will post after about 20 seconds or more, other times it won't post at all and I have to copy, discard and try again or refresh the page.
Sometimes I give up and look back later and it's been posted. This has been the cause of my semi regular double posting.
I don't have the issue from Firefox or Chrome on Android, Windows 7 or Windows 8.1 (I use all of them regularly).
Perhaps the pending update will sort this out.
If the update doesn't resolve it, then I'll post it over on the node.bb site.
</threadjack>
-
Mine seemed fine today. Might have been the wireless.
