I know all about CSS and bandwidth saving measures - which is why the download pages went javascript a long time ago

However.. in reality.. the forums consume about 1/18th of the 7000+GB that gets used on the site monthly, so it is not an issue.

Besides, most of the people with large forums who whine about bandwidth are doing so because they don't have mod_gzip enabled (mod_deflate in apache 2.x) which compresses pages to 1/6th its original size anyways (even at its most basic compression level).

___________________

"In a world of illusion you only see what you feel"

thanks for explanations. gzip is a wonderful thing, i know
since you are following this thread, just wanted to let you know that the in-forums or in-thread search (the field on the bottom right) always gives an error... i guess it's due to all the changes that you did to search. could you also, if you have time, explain what you've done to search. i assume, you brought it to a separate database? i just like to know, might i do this for my own forum (very small one). thanks.

___________________
writing lyrics aint what it used to be

quote:

Originally posted by Swamper Thread Preview (surprisingly) seems intensive but isn't, when you retrieve all the thread info from the thread table there is also a left join on the icon table to obtain icons (if any) for that particular thread (within the same query) - a left join is also done on the post table to obtain the preview text of the first post (whose postid is already within the thread table). In order to handle the ignoring of users I would have to throw the user table into the fray and check that as well - it may slow things down a bit - and - I would try it, but, to handle the 0.0000001% of cases when it would matter - seems pointless to me.

Del, can't you just load the ignore list once when the session starts (or when the ignore list is changed), store it in a session variable, and write the filtering code in the PHP script instead of the SQL query?

There's no need to do another join - just query the ignore table by itself and use PHP to do the real work. That's basically one query per login, doesn't seem like a big slowdown. Most people don't have more than 10 or 20 users on ignore so it wouldn't be that memory-intensive either (300 users * 20 names * 30 char string ~ 180k).

Hell, I'll write the code for you if you want (assuming I can figure out vB).

___________________
My party schedule:
2009-02-21 - DJ Attention @ I'm So Popular
2009-06-18 - DJ Annoying @ People Need To Know Where I'll Be
2012-11-32 - DJ Insufferable ɸ Or At Least the Stalkers I Complain About
2048-06-66 - Spastic & Whocares ¶ Although I'm Actually Flattered
9999-45-81 - Tweaker Gimp ☼ I Probably Won't Even Go To This But I Have To Make Sure I Fill Up All The Available Space Here