IIS and SQL Server, Please help us

Phuoc,

There are many possible mainly in these categories:
1) contention and blocking due to programming design
multi-threaded C++ ATL Com modules is the highest performing
technique
2) SQL Server configuration: memory allocation and use of indexes
3) leaks in custom programmed modules that cause memory to fill up over time

I am a consultant and willing to help you right now either on-site or via
internet.
A year ago I built the IFPNET.com site (weather monitoring) which includes
the
following:

* 2.5 GHZ PC with dual-redundant 60 GB disk drives
* 2 GB Ram
* Windows 2000
* IIS 5
* SQL Server 2000
* DB access via custom C++ ATL objects using ADO

* over 10 million records in online DB 2GB in total size and climbing
* supports 30-50 concurrent users doing DB queries
* queries against 10 million rec table take 5-10 seconds to return results
in graphical form
* simultaneously receives and logs weather telemetry from over 100 stations
* simultaneously sends email and telephone alerts to users

This multi-threaded system (~20 threads) was optimized and tuned over
several months
both by testing and by numerous consulting sessions with Microsoft support.


See the slide show of the IFPNET example site off my 'consulting' link at
amfox.


Charles

http:\\www.amfox.com\consulting.htm

"Phuoc Linh" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
news:C6DFD313-6E49-44F8-9921-FA6F74FC9709@microsoft.com...
 > we would like to seek your advice in dealing with a technical problem that
occurred to our application recently as follows:
 >
 > Hardware includes: IBM server x220, PIII, 1.2 GHz, Xeon, HDD 36 GB, RAM
 > 1
 > GB. Software includes: Operating System: Windows 2000 server; Database
 > server: MS SQL 2000 standard edition server.
 >
 > Application includes: developed on VB Script, ASP technique. 10 modules
having about 1500 files each (15,000 files in total). Each module occupies
about 9 MB (size on disk). Using ADO for data accessing. IIS
 > configuration:
 > Application protection mode: High (isolated), ASP file caches maximum:
 > 255,
 > ASP engine caches maximum: 120.
 >
 > Problem: The application ran OK with some 1 or 2 programmers testing the
modules but the server was not able to function when some 10 users accessing
the application at the same time. At that time, Event Viewer did not
indicate any error. Total memory in use increased up to about 2 GB and all
the screen PC become blank. We had to restart the server or the IIS once
again and again. This often occurred after 30 - 60 minutes.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS and SQL Server, Please help us