That explains the 'Server too busy' page yesterday...
-
The Daily WTF got dugg.
UPDATE: That probably wasn't the cause, since this should have happened in the afternoon to evening hours. Still of some interest to those here, though.
-
Neat. Good to know that the server didn't feel the "digg effect" if such a thing exists (I'm still afraid of /.).
The server too busy is a result of the worker process sucking up offensive amounts of ram (1.2GB at last check) in order to cache things. I don't know why or what it's doing, but I've scheduled them to doubled the ram to 4gb on sunday morning. I've also set the process to recycle memory after it hits 500meg or so.
-
@R.Flowers said:
The Daily WTF got dugg.
You might say Digg Dugg us, if you played too many video games over the years.
-
@R.Flowers said:
The Daily WTF got dugg.
UPDATE: That probably wasn't the cause, since this should have happened in the afternoon to evening hours. Still of some interest to those here, though.Is it just me or is there a little bit of WTFery in the digg forum software? What is the point of those "below viewing threshold, show comment" entries?
The text of the "buried" entry is briefly shown during the showing / hiding animation, but there's nothing there (not even hidden text) when the entry is fully expanded.
So is the "bury" feature just there to give extra attention to the "buried" entries because something moves when you click on them?
-
@Phil the ruler of heck said:
@R.Flowers said:
The Daily WTF got dugg.
UPDATE: That probably wasn't the cause, since this should have happened in the afternoon to evening hours. Still of some interest to those here, though.Is it just me or is there a little bit of WTFery in the digg forum software? What is the point of those "below viewing threshold, show comment" entries?
The text of the "buried" entry is briefly shown during the showing / hiding animation, but there's nothing there (not even hidden text) when the entry is fully expanded.
So is the "bury" feature just there to give extra attention to the "buried" entries because something moves when you click on them?
It's pretty much like /.'s threshold: comments get "moderated" (noted by the users) and those below your user-set (or the default if you're not logged in) threshold get replaced by this placeholder.
The point of the "bury" feature is that you don't have to read buried posts.
If the text of the buried entry is not displayed when you ask for it, then there is a problem (in their script).
