From Woot Wiki

dswebhost: A word to the wise, during a woot-off turn off apache logs or they may quickly take over your server causing things to break. Everything should be back to normal and the server should remain stable. -- Darkstar 23:09, 30 January 2007 (UTC)

If you turn off your logging, how will you know what happened after the dust settled? Normal Apache logging shouldn't be a bottleneck. Of course if you are logging host names (if you have reverse lookup on) then you should probably turn that off. Or you could move to a less server-intensive WootOff checker implementation. -- S. Gartner ^talk 01:53, 31 January 2007 (UTC)

It's not the logs themselves, it's where they're being saved to. I could easily change the directory but to be honest, I don't need all that taking up space. I know how it's working and don't need to see who's accessing what, that's why I implemented a counter that keeps track of pages visited. As for possible errors, it hasn't logged anything useful so far since the PHP is sound. The only problem at this point (since I only just added it) is the AJAX and that's client-side. I can see that on my browser. Hostname logging is off and my woot-checker loads in ~200ms when loading the cache, ~700ms -1000ms when fetching information and fairly straight forward, not too many conditions. I was going for efficiency. Everything seems to be running very smoothly now. -- Darkstar 05:47, 31 January 2007 (UTC)

Just a tip. Leave the stats on, that way you can find people abusing your site by stealing bandwidth. Two of us found a site that put our checkers in iframes, and refreshed them every 30 seconds. I don't like theifs (especially because they were using an ajax checker)... -- ircmaxell 10:30, 3 February 2007 (UTC)

I found it because I made a counter I added to my pages that gives me $_SERVER['HTTP_REFERER'] along with time accessed and IP. -- Darkstar 03:31, 5 February 2007 (UTC)