Can we increase posts per page?
-
To like 50 or 100?
It takes about 20s to load something like 10 posts, chances are a lot of that is disco overhead, but sql should generally have improved performance because there will be less need to load posts frequently since it takes longer to get through the posts, thus enabling more idle time to pull posts.
Sql is really good at batching things, loading 10 posts at a time from a large sql store isn't actually very efficient. Granted, the number of rows should be fucking instant anyway because this is a god damn forum that doesn't generate that much data in the grand scheme of things, but i digress.
Also, are we taking applications for forums written by tdwtf members, because I've about had it with browsing this mess on mobile.
-
To hear the @discodevs tell it, the problem is all the badness (and you should feel bad!) of your Android device. Because it doesn't process the Javascripts efficiently enough. So, quit
and just enjoy the slow experience. Or go get an iPhone, because that will also further improve everyone else's experience once you give up on trying to post from the broken POS that is the iExperience, thus meaning fewer new posts for everyone else to load. But hey, at least the Javascripts will render blazinglyfast on your iJavaScriptDevice.
-
Also, are we taking applications for forums written by tdwtf members, because I've about had it with browsing this mess on mobile.
We have topics in the migration category about "t3k4" by @tar and "Discord" by @Captain.
If you think you could do better, go ahead!
-
10 posts were split to a new topic: Not spam for some project @accalia is doing
-
Sorry about derailing the topic with my stupid joke.
The batch size is 10 on Android, 20 everywhere else. The discodevs claim they had to do it this way because JS on Android is 7 times slower than other platforms.
Everything in engineering is a trade-off. A larger batch size would mean rendering each batch would take longer, but you would pay this penalty less often. The discodevs decided on rendering the batch more quickly, but paying that (smaller) penalty more often.
-
To like 50 or 100?
That means being jellypotatoed 50 or 100 posts at a time instead of 10. No thanks.
-
The batch size is 10 on Android, 20 everywhere else
Though, since they use a highly effective User Agent Detection method to figure out which devices are Android, the batch size for Windows Phone 8.1 is also 10.
Discourse, the forum for the next 10 years, using the technology paradigms of the last 10 years.
-
To like 50 or 100?
They used to be. Sam moaned that it was a detriment to performance and restored the default and removed the widget from the site settings:
On Andorid, you will literally cripple devices if you load 30 or more posts at once. Would be ok on iOS for the most part. We do not allow control of this because people set it to values that cause a catastrophically bad user experience. Which we get blamed for.
Search for Android and slow here if you wish to learn more.
-
-
What's a page?
-
An errand boy. However, I've never met a young boy who could carry 50 or 100 fence posts at once.
-
You're not whipping them hard enough.
-
-
It takes about 20s to load something like 10 posts
Did anyone else think "here's TRWTF" as soon as they read this?
-
It's funny because browsers, even old Android devices, would be able to easily handle literally 1000 posts at a time if it weren't for the Javascript overhead.
-
It's not funny. It's depressing.
-
Maybe not literally 1000 posts, but I suppose it depends on your DOM. Chrome starts crapping out on my device at about 50k-word dissertations. Granted, that's not posts, but it would be fairly equivalent... And that's just text! Imagine if it included links and images and all the other stuff that decorates posts!
-
Why not download fifty or a hundred or so posts all at once (which shouldn't take very long), and then render them to the DOM a few at a time just off-screen (which also shouldn't take very long)?
-
Why not download fifty or a hundred or so posts all at once (which shouldn't take very long), and then render them to the DOM a few at a time just off-screen (which also shouldn't take very long)?
Have you met Jeff?
-
It was a rhetorical question.
-
And mine was a lame joke. What's your point?
-
Why not download fifty or a hundred or so posts all at once (which shouldn't take very long), and then render them to the DOM a few at a time just off-screen (which also shouldn't take very long)?
That wouldn't work, the user's position on the page would jump aro-- oh.
Well anyway, it would break the scro-- oh.
-
-
Is Ted a dick?
(I didn't really watch that show, so...)
-
No, it was Barney's way of introducing him to girls in the hope that Ted would either get laid, or bore the girls so much that they'd be easy targets for Barney.
