LQ slows down every few hours. Logging out solves the problem.

damgar · 05-15-2010, 07:05 PM

Hmmmmmm. It's happening on multiple machines. I'll see how the no caching goes. The machines and the connection are both fast enough that they shouldn't need the caching anyway.

exvor · 05-16-2010, 06:13 PM

I am thinking this has something to do with info that is saved on the local machine esp since they can navigate away and it gets resolved. Temporary login cookie maybe? It may explain my weird log out issue as of late.

I have not done any testing tho to try.

Larry Webb · 05-17-2010, 06:52 AM

Quote:

Originally Posted by damgar

It happens when following links such as from LQ spy, or from the forums page to the specific forums, or from inside a forum to a specific thread.

EDIT:

Also when submitting a reply when returning to the thread.

I submitted a post in an earlier thread with same problems and cure the same from the Houston, TX area. This only seems to happen at approximately between 7:00 to 9:00 AM and 4:00 to 7:00 PM CST. I use a wireless modem so I blamed it on them. As you say it can be remedied by signing off and then signing back on.

jeremy · 05-26-2010, 10:32 AM

Is this continuing to happen for any members?

--jeremy

Larry Webb · 05-26-2010, 11:50 AM

I found my problem, I use Firefox and my wife uses another browser which I had as default and if she had used it to open a link it would cause my system to slow down until I shut my browser down and reopened. I presume I am having a cache problem.

damgar · 05-26-2010, 01:43 PM

Quote:

Originally Posted by jeremy

Is this continuing to happen for any members?

--jeremy

Yes. Even with caching off.

jeremy · 05-26-2010, 01:49 PM

damgar,

The next time it happens can you send me the exact time along with a traceroute? Thanks.

--jeremy

damgar · 05-26-2010, 02:43 PM

Will do.

damgar · 05-27-2010, 08:27 AM

8:24 am 5/24/10

Code:

bash-4.1$ traceroute www.linuxquestions.org
traceroute to www.linuxquestions.org (75.126.162.205), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.081 ms  1.311 ms  1.528 ms
 2  10.244.96.1 (10.244.96.1)  26.983 ms  33.514 ms  83.839 ms
 3  s66-76-81-141.mnttmo.sta.suddenlink.net (66.76.81.141)  84.231 ms  84.533 ms  84.870 ms
 4  s66-76-81-129.mnttmo.sta.suddenlink.net (66.76.81.129)  85.240 ms  85.551 ms  85.872 ms
 5  173.219.254.48 (173.219.254.48)  86.641 ms  86.934 ms  87.252 ms
 6  64.211.195.141 (64.211.195.141)  86.259 ms  21.629 ms  53.324 ms
 7  te2-1-10G.ar3.DAL2.gblx.net (67.16.129.118)  53.027 ms  53.795 ms *
 8  te3-6.bbr01.eq01.dal01.networklayer.com (64.215.81.2)  63.103 ms *  63.395 ms
 9  po2.fcr02.dal01.networklayer.com (66.228.118.182)  63.783 ms  64.094 ms  64.343 ms
10  www.linuxquestions.org (75.126.162.205)  61.039 ms  61.300 ms  61.570 ms
bash-4.1$

Since really paying attention (since yesterday's request for traceroute) it seems that the issue seems to resolve itself after a bit. There have been some slowdowns, but I was trying to make sure before I gave you anything false to troubleshoot with. I may just be picking up on something because I'm looking for it. I know that's of no help. It's possible the issue has been resolved.

jeremy · 05-27-2010, 08:44 AM

If the above was during one of the slow periods we can rule out connectivity being the issue, which means it's local to either you or LQ.

--jeremy