It's hard to say -- depends on what their doing, and if you're on a shared server, it depends on how busy the server is. If you're load is below 2 all the time, you shouldn't worry about this hack too much. :)

does this hack reduce also the server-traffic ?

I don´t care about the serverload, but traffic is a important thing to me.

How about 130+ ? I'm trying to decide if the issue of a server crash is worth the speed increase. (e.g. if the server dies prior to this hack actually writing to a 'real' table, the counts will be lost?).

No, the traffic isn't affected in any way.


I'm pretty sure it'll make a big difference at 130+. :) But, yes, if the server dies, you'll lose the threadviews since the last update. The way I see it, if the server is crashing, you've got bigger problems to worry about than thread views. :p

We are loping along at 400 users on line and it seems to be working great, the updates are happening every 1-2 minutes with a savings of from 7-40%...I am not sure what ideal is

Since you're on a dedicated server you can afford to have more bulk updates. I'd suggest cranking up the second number (default is 600) in the mt_rand function so that updates take place less often. 40% is ok, but 80% would be better. :)

Ok let's try a 1000 and see what happens :)

I think a 1000 might be a spec high!

4431 Total Views (original number of write queries)
1310 Threads (new number of write queries)

3121
Writes Avoided (70% avoided)

Yowza! 1300 queries... :paranoid:

Keep tweaking :)

I'll install this tomorrow and give it a whirl :)