im not complaining, tww is a great free service!!1 but i am curious (omg haxrs)everything else is as fast as normal, but it seems like lately that it takes a good 10 seconds to get a reply from tww after i submit my username and passwordis it broke, yo
2/25/2009 8:26:04 AM
very slow. ads fuck it up.mods could raise $texas buy selling $10 12-hour RD bans.
2/25/2009 8:28:14 AM
OMG SEARCH
2/25/2009 8:28:41 AM
jackleg
2/25/2009 8:29:46 AM
search what, this is chit chat, this thread will be forgotten soonplus its just the one thing, the login. seemed weird. i wanted my own threadOK
2/25/2009 8:31:31 AM
nope, it's super fast for meFASTEST WEBSITE EVER
2/25/2009 8:32:19 AM
TWW IS PERFECT!
2/25/2009 8:32:48 AM
considering the amount of traffic and amount of data, it honestly is super fast
2/25/2009 8:33:25 AM
message_topic.aspx?topic=538529the fucks in feedback never forget
2/25/2009 8:44:07 AM
tww is always slow
2/25/2009 8:45:15 AM
^ it didn't used to be this bad...it's only been since new management
2/25/2009 8:46:24 AM
it was a joke
2/25/2009 8:47:08 AM
i dont think it has anything to do with the management. i'd like to hear qntmfred's take on it. i have a "theory"
2/25/2009 8:49:03 AM
^ i think it has to do with the management in terms of the attempt the increase ad revenue and perhaps a change in hardware (i figure it's possible they moved everything over to cheaper servers when they bought it, but i don't know for sure)*shrug*[Edited on February 25, 2009 at 8:51 AM. Reason : .]
2/25/2009 8:50:51 AM
2/25/2009 8:52:00 AM
every time i navigate to TWW for the first time, it takes a good 20secs for it to load (at least) and it always goes to the "OH SHIT INTERNAL SERVER ERROR" screen, at which point i promptly click HOME and start navigating from there. i would say 1 out of every 10 times, i get a RUNTIME ERROR instead of the OH SHIT screen, at which point i close out the window and start again.this is EVERY TIME i come to TWW for the first time. if i close out and come back 5 mins later it works OK though, cuz the page is still in the cache, but several hours later - no dice, it's gonna take forever to load again.been like this for awhile, at least a few months. i thought i was the only one
2/25/2009 8:52:02 AM
2/25/2009 9:46:21 AM
2/25/2009 9:48:56 AM
it is related to login. there's an authentication stored procedure that times out b/c the session list table is fubar. i have some ideas on how to fix it, but last time i tried it, the db choked on it every time.
2/25/2009 2:24:30 PM
F5F5F5F5and it's only slow at work, stupid P4/512MB slugbucket
2/25/2009 2:25:25 PM