一个1000个用户的应用程序 [英] an application for 1000 users
问题描述
我想创建一个应用程序，其中大约1000个用户将同时提供
。所有用户将发送大约1 MB的
数据。我将解析该数据，并将一些数据
插入到数据库中。
这种Web应用程序是Web服务的正确选择。什么
我可能遇到的一些性能问题。对于这种应用程序，ASP.net是否是正确的选择。并且IIS 6是否能够支持
这种网络服务。
问候，
Jamunt
你需要知道一个交易花费多长时间才能使用你想要使用的架构。 ASP.NET和webservices不会有这个卷的问题
的用户，但你的服务器硬件和网络管道可能都有。
阅读一些好文章关于规划和设计。扩大规模和架构
http： //msdn2.microsoft.com/en-gb/library/ms979199.aspx
http://msdn2.microsoft.com/en-us/library/aa478997.aspx
-
问候
John Timney（MVP）
访问我的网站：
http://www.johntimney.com
http://www.johntimney.com/blog
< Ja **** @ gmail.comwrote in消息
news：11 ********************** @ 80g2000cwy.googlegro ups.com ...
我想创建一个应用程序，其中大约1000个用户将同时提供
。所有用户将发送大约1 MB的
数据。我将解析该数据，并将一些数据
插入到数据库中。
这种Web应用程序是Web服务的正确选择。什么
我可能遇到的一些性能问题。对于这种应用程序，ASP.net是否是正确的选择。并且IIS 6是否能够支持
这种网络服务。
问候，
Jamunt
< Ja **** @ gmail.comwrote in message
news：11 ******** **************@80g2000cwy.googlegro ups.com ...
我想创建一个大约1000个应用程序用户将一次性提供
。所有用户将发送大约1 MB的
数据。我将解析该数据，并将一些数据
插入到数据库中。
这种Web应用程序是Web服务的正确选择。什么
我可能遇到的一些性能问题。对于这种应用程序，ASP.net是否是正确的选择。并且IIS 6能够支持这种Web服务吗？
用户数量不会对软件提出任何形式的挑战
你选择的
，只要你的硬件达到它和你有效地设计你的
系统。
然而，它不会为你自己做 - 你需要阅读
高效的设计实践，数据库并发和锁定问题，
可扩展性，故障转移等......
你的主要问题将是上传需要多长时间。对于一个网站来说，1000个用户不是很多，但是如果请求需要很长时间，那么你就会遇到一个
的问题。 iis只支持大约200个并发请求（默认
配置要低很多）。如果某些用户拨号或使用慢速的网络，你真的有500-1000个并发用户，那么你需要一个
的网络农场。你会想要配置web服务器和asp.net以获得最大的
连接以限制机器的数量。
- bruce（sqlwork.com）
Ja****@gmail.com 写道：
我想创建一个应用程序，其中大约1000个用户将同时提供
。所有用户将发送大约1 MB的
数据。我将解析该数据，并将一些数据
插入到数据库中。
这种Web应用程序是Web服务的正确选择。什么
我可能遇到的一些性能问题。对于这种应用程序，ASP.net是否是正确的选择。并且IIS 6是否能够支持
这种网络服务。
问候，
Jamunt
Hi,
I want to create an application in which around 1000 users will be
served at one time. All of the users will be sending around 1 mb of
data. I will be parsing that data and would insert some of the data
into the database.
Is web service right choice for this kind of web applications. What
kind of performance problems i might encounter. Will ASP.net is the
right choice for this kind of application . And will IIS 6 is able to
stand this kind of web service.
Regards,
Jamunt
You''ll need to work out how long a transaction takes on the architecture you
expect to use. ASP.NET and webservices wont have a problem with that volume
of users, but your server hardware and internet pipe may well have.
Read some good articles on planning and design. scale up and architecture
http://msdn2.microsoft.com/en-gb/library/ms979199.aspx
http://msdn2.microsoft.com/en-us/library/aa478997.aspx
--
Regards
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
http://www.johntimney.com/blog
<Ja****@gmail.comwrote in message
news:11**********************@80g2000cwy.googlegro ups.com...Hi,
I want to create an application in which around 1000 users will be
served at one time. All of the users will be sending around 1 mb of
data. I will be parsing that data and would insert some of the data
into the database.
Is web service right choice for this kind of web applications. What
kind of performance problems i might encounter. Will ASP.net is the
right choice for this kind of application . And will IIS 6 is able to
stand this kind of web service.
Regards,
Jamunt
<Ja****@gmail.comwrote in message
news:11**********************@80g2000cwy.googlegro ups.com...
I want to create an application in which around 1000 users will be
served at one time. All of the users will be sending around 1 mb of
data. I will be parsing that data and would insert some of the data
into the database.
Is web service right choice for this kind of web applications. What
kind of performance problems i might encounter. Will ASP.net is the
right choice for this kind of application . And will IIS 6 is able to
stand this kind of web service.That number of users will not present any sort of challenge to the software
you have chosen, so long as your hardware is up to it and you design your
system efficiently.
However, it will not do it for you on its own - you''ll need to read up on
efficient design practices, database concurrency and locking issues,
scalability, failover etc...
your main issue will be how long the uploads take. a 1000 users are not
many for a website, but if the requests take very long then you have a
problem. iis will only support about 200 concurrent requests (default
config is a lot lower). if some of the users are dialup or use slow
networks and you really have 500-1000 concurrent users you will need a
web farm. you will want to configure the webservers and asp.net for max
connections to limit the number of machines.
-- bruce (sqlwork.com)
Ja****@gmail.com wrote:Hi,
I want to create an application in which around 1000 users will be
served at one time. All of the users will be sending around 1 mb of
data. I will be parsing that data and would insert some of the data
into the database.
Is web service right choice for this kind of web applications. What
kind of performance problems i might encounter. Will ASP.net is the
right choice for this kind of application . And will IIS 6 is able to
stand this kind of web service.
Regards,
Jamunt
这篇关于一个1000个用户的应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
