I think we can make everyone happy
-
- Click on "Pancakes".
- Click on "Admin".
- Click on "Settings".
- Click on "Basic Setup".
- Scroll down to the bottom. This is what it will look like:
- Change the values to something more reasonable. Example shown:
Congratulations. You have now upgraded your Discourse installation to a far superior Intercourse.
- Click on "Pancakes".
-
Done!
-
Careful. Serious performance implications, as page load time rises basically linearly with the number of posts.
So the tradeoff is, less chunking but slower load time for everyone on all topics, all the time. Can't say I'm a fan, but try it out and you decide.
(Each post has a bunch of Ember.js JavaScript hooks that are applied, and the more posts you have..)
-
Careful. Serious performance implications, as page load time rises basically linearly with the number of posts.
Yeah, page load time tends to be based on the number of things on the page. Not really much we can do about that unless we can process each item faster than constant time.So the tradeoff is, less chunking but slower load time for everyone on all topics, all the time. Can't say I'm a fan, but try it out and you decide.
I'd prefer a 5 minute video buffering for a minute before it plays over stopping every 5 seconds to try to catch up. Community Server had 50 items per page, so we're used to being able to scroll through 50 posts before having to load more. Now we can do that here, too!
-
-
It isn't actually linear depending on the device, on my iPad Air, topics (of more than x posts to begin with) now take about 3 seconds to render whereas with the defaults they took 1.
Will be dramatically worse on devices with slower CPUs than the Air, e.g. mobile, though I think we hard code load limits on mobile for this reason. (iPad is not considered a mobile device.)
Mostly wasted time, particularly when entering the topic at the bottom.
-
Mostly wasted time, particularly when entering the topic at the bottom.
It's not wasted time, it makes the scrollbar work for short threads.
-
I see posts per page is now 50. Page loading is now unacceptably slow for me, reminiscent of CS with a large tag blob.
I think this points to a severe performance problem in DC, rather than an unreasonable setting, since without the stupid tag blob, CS and all other websites can obviously instantly download and render 50 measly posts.
Edit
Jeff/Sam, are you aware of The Stupid Tag Blob in CS?
-
Same here. The site was much slower to load topics on my phone during my commute this morning.
-
I think we should keep it at 50 posts until the performance bug gets fixed.
I'm only half serious.
-
Personally I would much prefer that a bunch of blank divs were rendered, rather than this very awkward solution. I can already feel the site is a lot slower than it was and am struggling to understand the gain.
If people really want to render a blank divs for every post, so be it, I don't see what its buying them but whatever it is its way better than what is going on now, here.
We don't even render these extra posts that are buffered, its just weird upfront client side work we don't need to be doing.
(the post rendering keep only a limited amount of slack rendered, rest is in blank divs anyway)
-
5 minute video buffering for a minute
stopping every 5 seconds to try to catch up
Why not both?
-
Regardless of what the cause is, how DC works, or how it's fixed -- I don't actualy care too much about those details -- I really don't think forum software should have problems with 50 posts. Or 100. Or 200. It doesn't feel right in my humble world view.
In case it wasn't clear: CS had performance problems because it would load triple copies of every unique tag on the board in the html, causing some pages to balloon up to a megabyte. Note: Discourse is about as fast as a website articifially hobbled with a meg of crap data per page. Let that be your guiding line.
-
You fucking haggis. How dare you.
-
Hey, Ben's too young to remember it. Loss of history = doomed to repeat it, etc.
I'm saving the world.
-
I really don't think forum software should have problems with 50 posts.
I agree with you, but at the moment, we are waiting on an Ember upgrade. We are talking about the range of 20ms overhead to render a post, the offscreen stuff has other advantages that it keeps the DOM slim. If we could get it down to 1ms per post I would be very happy. But it will be a journey and the first stop is htmlbars.
-
ACCEPTABLEEEEE!
(I've set the posts per page to 30 for now)
-
In case it wasn't clear: CS had performance problems because it would load triple copies of every unique tag on the board in the html, causing some pages to balloon up to a megabyte. Note: Discourse is about as fast as a website articifially hobbled with a meg of crap data per page. Let that be your guiding line.
Not sure how much server performance makes a difference... but CS is hosted on a dedicated quad-core xeon somethingorother with 16gb ram. Discourse is on a comparatively dinky server... the $20/mo plan at Digital Ocean.
-
Ember.js code running from every post loaded is not a server problem, but a client problem.
We render realtime svg maps faster than this forum loads... how can it seriously require THAT much js to display a stupid forum?
-
Does old post necro revival at the behest of suggested topics make anyone happy? @presidentsdaughter
[Rules](http://what.thedailywtf.com/t/the-official-likes-thread/1000/1107?u=drakesmith)
-
No.
-
-
[spoiler]<a/><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big><sup><big>2 letters does not a post make.[/spoiler]
Yay for Discurse's screwed-up quote formatting. I can't even make a quick, cheap joke without Discurse killing it.
@darkmatter said:2 letters does not a post make.
No, Discurse only requires one letter to make a post.
-
-
[spoiler][omitted]
-
On topic: No, I'm not fucking happy now.
-
-
I think that I am not ;)
[spoiler](doing it wrong, that is.) It sure feels so right anyway.[/spoiler]