urgent strange problem
Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=13942
Printed Date: 29 March 2026 at 10:57pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: urgent strange problem
Posted By: sunandoghosh
Subject: urgent strange problem
Date Posted: 22 February 2005 at 6:01am
|
Hi friends,
I am confronted with a very unique problem when trying to upload web wiz forum on my site and use it.
The problem is when i uploaded web wiz forum on my site with access as database, it runs extremely fast but when I upload the same forum with sql as database (which is what i desire considering merits of sql over access), i find that the speed of forum REDUCES tremedously.
In fact many times with sql as databse it does not open whereas with access as database, it always opens very fast. This is quite a paradox as it should have worked the other way round. I am still confused in the light of above as to whcih database to use for my forum anticipating large mebers in long run using the forum on my site. any inputs, comments, suggestions will be highly appreciated. Thanks once again. sunando |
Replies:
Posted By: WebWiz-Bruce
Date Posted: 22 February 2005 at 6:21am
|
What are the errors you are getting? (if you use IE you may need to turn of friendly HTTP error messages) If you are having speed problems with SQL Server and timeout problems then it can be because of a number of issues. It could be network congestion problems, the SQL Server is usually located on a different server to the web server, if there are problems on the network then this can course slowness. You usually want the SQL Server to be located on the same network as the web server, if you are trying to connect across the Internet it will always be very slow. Another problem could be that your host has packed to many SQL Server databases onto the same server and it is overloaded. Upgrading the server or having your database placed on a less populated SQL Server may improve things. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: dpyers
Date Posted: 22 February 2005 at 9:45am
|
Also, for your connection string, use sql server authentication, not windows authentication and stay away from dsn's. ------------- 
Lead me not into temptation... I know the short cut, follow me. |
Posted By: sifra
Date Posted: 21 March 2005 at 1:28am
|
I love the forum, but the SQL implementation definitely needs work.
I have run SQL Profiler traces on the following pages, and the problem is mainly server side cursors. Each cursor fetch is a round trip call to the server, and many of the pages have hundreds of database calls per page.
We have found when the number of users on an active forum (>150,000 threads per quarter) exceeds a few dozen users, the ability of SQL Server to keep up with the cursor fetch demand, even on a co-located server is severely challenged.
default.asp, forum_topics.asp, active_topics.asp are prime examples.
Another problem is revealed when you run the following command in Query Analyzer
EXEC sp_MSforeachtable @command1="sp_help '?'"
Notice the twins? They do not improve read performance, but definitely hurt updatable operations.
The table structure is also very poor, with fixed data types intermixed with variable length types. For example, all bit data types should be contiguous. Why? SQL packs contiguous bits into a single byte of storage, saving space and improving performance by reducing logical I/Os, ie page density increases thereby reducing page reads. I am not referring to tblPermissions as the bits are contiguous there.
Another problem is that every time a recordset is to be opened, a check is performed on whether Access or SQL server is to be called. The entire data sets for the web sites for each provider should have been isolated in function calls in individual include files. This would allow the code base to play to each database's strength.
Client side pagination using ADO is one of the worst possible performers (see http://www.aspfaq.com/show.asp?id=2120 - http://www.aspfaq.com/show.asp?id=2120 ). In the current implementation, all the records are thrown over the wall from SQL Server to the ADO layer, where the paging is done. On large forums, most of the pages will never, ever be visited by an end user. It is a huge waste of CPU, bandwidth, and memory to fetch more records than will actually be viewed by the user.
There is more, but it is my bedtime. All of the deficiencies are relatively easy to address, and it makes a huge difference in throughput when they are corrected.
 |
Posted By: WebWiz-Bruce
Date Posted: 21 March 2005 at 4:45am
|
Please see the development blog for version 8:- http://forums.webwiz.net/forum_posts.asp?TID=13860&PN=1 - http://forums.webwiz.net/forum_posts.asp?TID=13860&PN=1 You will see that most of the things you mention are already been worked on have been implemented for version 8. For example the pages default.asp, forum_posts.asp, forum_topics.asp, have all been re-written to use arrays for the recordset paging and have had database calls reduced to 3 to 4 maximum per page. The rest of the files are being worked through at the moment to also improve performance abd reduce database calls. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |