TiVo Community Forums Archives - "Fix" for server overload?

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

"Fix" for server overload?
(Click here to view the original thread with full colors/images)

Posted by: TivoGeezer

I had noticed the past couple days that, in the afternoon, I would get errors about too much server load to return to the "New Posts" listing after visiting a thread. I think this was because going back to the listing would automatically do another search and refresh the list and, if there are 600+ logged in users, many reading new posts, that the server was going nuts doing searches. It looks today that the automatic refresh of the list has been removed and a manual refresh is now required to see the latest new posting list. I am guessing this was done to reduce the massive number of searches which were causing the overloads. Am I right or am I right?

Posted by: dswallow

http://www.tivocommunity.com/tivo-v...664#post1608664
http://www.tivocommunity.com/tivo-v...027#post1624027
http://www.tivocommunity.com/tivo-v...618#post1624618

Posted by: TivoGeezer

Doug, I saw that thread and none of it seemed to have anything to do with the thing I was describing above. Perhaps I am wrong and the caching affects it but I am not that savy on how browsers work internally anyway.

But wouldn't you know, now the list looks like it IS getting refreshed when returning from a thread. Go figure.

Posted by: dswallow

quote:
Originally posted by TivoGeezer
Doug, I saw that thread and none of it seemed to have anything to do with the thing I was describing above. Perhaps I am wrong and the caching affects it but I am not that savy on how browsers work internally anyway.

What was happening was the pages from TC were being issued to your browser with instructions in the header that they expire from the browser's cache immediately so every time you move back or forward using your browser's navigation buttons it would re-request the page from the server, which is why you were getting an automatically refreshed list everytime you moved around.