I'm no programming square, so why should a page of a large thread take any longer to appear...

[dug777]

to load the last page...

In my mind, a page of a thread should be no harder to lookup and display for a large thread than for a smaller thread...

A thought occurs to me, that would be true for a set 'thread view size', but since we are all free to choose our 'thread view size', the server must process each thread based on this individual parameter, it would logically take longer to 'order' a longer thread into groups of 30, or 40, or whatever you have set...

I suspect i've answered my own question, but if i have, you still wouldn't think it would take THAT much longer to order and display...

Also, a belated HAPPY NEW YEAR to y'all :beer:

 

[loup garou]

Not that I would expect an answer as to why, as I don't think AT employs anyone "programming square" anymore, but I've noticed that the slowness seems to be tied to threads with a large number of views, more than replies. Which makes even LESS sense. 😕

 

[MmmSkyscraper]

When the forums were having their slow period in November(?), I had more trouble looking at the first page rather than the last. That's pretty much disappeared now, but it does leave you feeling totally 😕 when this stuff happens.

 

[Roguestar]

The threads with thousands of posts take longer to load because the server has to query the database for the thread and once it has been found, load at most 40 posts for a page. It's the getting the whole response from the database of 40 posts from a much larger record that takes somewhat longer than a 40 (or even less) post thread.

 

[gsellis]

Originally posted by: Roguestar
The threads with thousands of posts take longer to load because the server has to query the database for the thread and once it has been found, load at most 40 posts for a page. It's the getting the whole response from the database of 40 posts from a much larger record that takes somewhat longer than a 40 (or even less) post thread.

Reworded for the non-programming square, a page is not a page as you are thinking of it. So, to pull a page (I have mine set for 50 per page displayed), it must do 50 SQL calls to get each item and then put it in an HTML page. More entries, longer delay. Your browser is doing the work, so you have influence over how poorly it is working. And if the indexes aren't optimized or poorly designed, it gets slower with more posts on the server. And there can be a number of reasons the server can be slow. And it just might not be your ISPs day for speed too.