|
IIS 6.0
Aprés IIS 5 et
5.5 voici la suite enfin attendue par tous,
Plan de la présentation
l
Performance/Scalability features of Windows® .NET Server in Web infrastructure
l
Programming Environments
Ø
ASP .NET
Ø
ASP
Ø
ISAPI
l
How should I build my applications to take advantage of Windows .NET
Le Focus on the performance and scalability features of IIS 6.0. Topics include: taking advantage of the kernel
mode cache, performance API, workload affinitization configuration for scale-up, and scale-out capabilities.
Eric Deily
Eric Deily works as a Program Manager at Microsoft Corporation for the Internet Information Services (IIS) team. Responsible for IIS 6 platforms, Eric designed the extension of services like HTTP.SYS, Web
administration, and process modeling. His previous work experiences include software release management, Web development, and network management.
IIS 6 travaille dierctement avec le KERNEL,
Quand une demande est faite est dans le cache pas de transactiion inutiles.
Les performances sont accrues,
 2 fois plus de rapidité de réponses avec II6
Vous pouvez supporter des 10 000 de logs sur le sites.
Cela est limité aux capacité de la machine « mem. Consomme ».
 Cela devient simple à installer
Envirronnement de prog. Manage code ou Unmanage code :
VB , C etc.
Pour avoir plus de contrôle, une application a à être « scalable »
 Faire fonctionner des applications ASP
Comparaison entre Win2000 et Win.NET répons
ISAPI Considerations
l
C++/native code through ISAPI
Ø
Do NOT do your processing on the ISAPI thread
Ø
Always send using asynchronous send APIs; ISAPI on Windows .NET Server is no longer tolerant of synchronous writes – performance will suffer
Ø
Use VectorSend/FinalSend combination
Ø
Where possible cache responses
Ø
Cleanup in TerminateExtension() calls – they will be called frequently
Ø
Review use of ISAPI Filters and if possible try and remove
ASP .NET Considerations
Ø
Output cache using kernel
§ Better
performance than current output cache
(kernel served)
§ Should
consider what information needs to be absolutely current and what information can be
a little stale
Ø
Fragment cache
§ Use for
expensive-to-construct portions of pages
Ø
Run in-process
§ All
processing done in-process
§ Default
on Windows 2000 involved a
process hop
§ Try to
stay in managed code – avoid
Interop if possible
§ If you
are running Interop scenarios run
COM object in process
Ø
Intrinsic gains in ASP .NET on .NET Server
§ ASP
.NET leverages new ISAPI features
§ ASP
.NET/IIS implement a fast path for common case response headers
What Should I Do Now?
l
ISAPI
Ø
Review for best practices
§ Don’t execute on the IIS thread, maintain small threadpool
§ Use Async IO wherever possible (that includes using Async version of VectorSend and WriteClient()
Ø
Re-architect ISAPI filters into extensions
Ø
Consider changing WriteClient calls to VectorSend and specify FinalSend flag when complete
Ø
Determine if certain dynamic responses can be stale; If true, cache them
 Non utilsable à ce jour, bientôt béta prog. 2003 début
Resources (visiter)
l
Internet Information Server (IIS) 6 Overview
l
ASP .NET Performance Tips
| 
SharePoint
au
Quotidien
avec
EROL
