Re^2: Does the monastery want a threaded newest nodes?

Im not sure about the load issue. How does it compare for you to newest nodes? And is the timing consistant when you do a refresh? Also are you using it in "day mode" or "time mode" (ie did you use the "I've checked these" button or not?)

---
demerphq

_{First they ignore you, then they laugh at you, then they fight you, then you win.

-- Gandhi

Flux8}

Comment on Re^2: Does the monastery want a threaded newest nodes?

Replies are listed 'Best First'.
Re^3: Does the monastery want a threaded newest nodes? by meredith (Friar) on Sep 22, 2004 at 18:19 UTC
Day mode. Human-timed, I get Newest Nodes at about 5 seconds, and yours at about 17 seconds. That's not bad, considering the extra work of finding children. (I do hate gathering the children, after they've run all about the monstery.) `mhoward - at - hattmoward.org`	[reply]
Re^3: Does the monastery want a threaded newest nodes? by Happy-the-monk (Canon) on Sep 22, 2004 at 22:54 UTC
Timing like hattmoward did, I get 13 seconds for both, so I see no time-to-load issue for me. I am very impressed by the looks of it (++demerphq's work). I am also very happy with the new usability too. Yay! What I like to preserve though is that PM isn't working too much the same way Usenet News does - at least in my perception. All questions on top, waiting for people to find answers to them. Presented in this way ,PM's newest nodes look more like Usenet, threaded and such... well, we will see it evolve. Cheerio, Sören	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks