bmwracer wrote:Here we go again: Anyone notice any sluggishness in accessing Jdorama?
I noticed it, it's not just you. About an hour or two ago it got slower and slower then choked.
But then when it came back in a few mintues it was fast.
edit: dang, looks like it's happening again. I'm getting ping times of over 1000ms. :bleh:
Whew, I just decided to log in since the speed started to return to normal. It was weird, my browser would neither display pages or return an error saying the page (or site) does not exist.
dochira wrote:It was weird, my browser would neither display pages or return an error saying the page (or site) does not exist.
Correct, because it was working, just very slowly.
Opening the TCP connection was slower than normal but still took a few seconds at most. That's why no error is reported within the first couple of minutes.
However, then getting the HTTP response in answer to the request could take many minutes at the maximum delay I saw last night. If your browser had a high enough timeout setting, then it would eventually get the response and display the page. Otherwise, the browser should have displayed an error once the timeout was reached.
ccwf wrote:However, then getting the HTTP response in answer to the request could take many minutes at the maximum delay I saw last night. If your browser had a high enough timeout setting, then it would eventually get the response and display the page. Otherwise, the browser should have displayed an error once the timeout was reached.
Hmm, I've always wondered: is there a way/where to change that timeout?
bmwracer wrote:Hmm, I've always wondered: is there a way/where to change that timeout?
Well, if you use firefox (and you should, since MSIE is such a piece of poo :P ), then type "about:config" in the location field and hit return.
Then you can type "timeout" in the filter field and it will show you the timeouts you can alter.
The 2 timeouts you probably want to consider would be network.http.request.timeout and network.http.connect.timeout. You can try increasing them to whatever you desire.
As for me, I probably wouldn't muck with it. I think the defaults are pretty reasonable, and if the site is that slow, I'll just come back later.
I don't really want to work with a slow site as it will just make it slower. :sweat:
bmwracer wrote:
Hmm, I've always wondered: is there a way/where to change that timeout?
If using Mozilla/Firefox, go to about:config (the board won't let me enter a link to it) and change the network.http.request.timeout and/or network.http.connect.timeout settings. You'll see there are lots of other settings that can be adjusted, too.
For Internet Explorer, create a ReceiveTimeout entry using regedit in [HKEY_LOCAL_MACHINE/Software/c/InternetSettings]. The exact registry path will vary from machine to machine.
loris wrote:you should, since MSIE is such a piece of poo :P
Can't do that: Microsoft is king here. :sweat: :sweat:
As for me, I probably wouldn't muck with it. I think the defaults are pretty reasonable, and if the site is that slow, I'll just come back later.
I don't really want to work with a slow site as it will just make it slower. :sweat:
I suppose you're right... Gets frustrating when I can't get my Jdorama fix... :beaten: