Slow Default.asp load time

See if you got a lot of PMs in your database and delete them periodically, if you got a whole bunch it takes longer for the database to query for new PMs.

If you need the active users then remove the ones at the bottom, no need to have them twice. Also if your nav bar is the mod that's posted here I just looked at it and it hits the db once for each member to get the username so if you got 10 members online is 10 xtra hits, plus one you use on your site to get the count of active users on the button. It can all be gotten with one, later I will post the one I use in my site as a mod, it gets the amount of members, the amount of guests, and the list of members with 1 hit...

What I did was I removed the hit for the Configuration and placed it into a configuration file. One hit gone.

I created a join to join the categories and forums. That reduces the category and forum calls (which increases with every forum added) to one query.

I returned all the permission for the user in one recordset which I set into an array.

and then I took the above along with the rest of the queries on the page and stuck them into one stored procedure and thus all that information is stuck into one database call.


Ideally, the database would be rewritten as well. Currently the database is as extremely normalized. By removing some of the normalization, it would make for a better design for the application. First I would add a column for the last post and the last author to the forum table along with the topic and post counts. This same method would follow into the topics area. This would allow direct joins between one or two tables rather than complex joins over multiple tables.

For permissions, I would use a stored procedure to create a temp table with the forum information and the base permissions and then update those base permission in the temp table to whatever the permission table altered the value to.

There are more things that I would change but those mentined would increase the performance of the forum by placing more of the SQL processing on the SQL server and less of the processing through ASP and multiple SQL calls. This is something that can easily be done with SQL Server, but impossible with Access. If the goal is to continue to support Access and SQL, then I would suggest moving towards saving recordsets into array so that the database recordsets can queried and set aside for later processing.