亚洲人成网址在线观看 ,中文字幕无码精品亚洲资源网,国产精品日本亚洲777

MySQL服务器安装完之后如何调节性能

becket_zheng — Tue, 30 Mar 2010 09:00:00 GMT

MySQL服务器安装完之后如何调节性能

译者：(x��)叉��荣（Email:�Q�，转蝲��h��明译者和出处�Q��ƈ且不能用于商业用途，�q�者必�I��?br />
My favorite question during Interview for people to work as MySQL DBAs or be involved with MySQL Performance in some way is to ask them what should be tuned in MySQL Server straight after installation, assuming it was installed with default settings.
在面试MySQL DBA或者那些打��做MySQL性能优化的�h�Ӟ��我最喜欢问题是：(x��)MySQL服务器按照默认设�|�安装完之后�Q�应该做哪些斚w��的调节呢�Q?br />
I’m surprised how many people fail to provide any reasonable answer to this question, and how many servers are where in wild which are running with default settings.

令我很惊讶的是，有多��h对这个问题无法给出合理的�{�案�Q�又有多��服务器都运行在默认的设�|�下�?br />
Even though you can tune quite a lot of variables in MySQL Servers only few of them are really important for most common workload. After you get these settings right other changes will most commonly offer only incremental performance improvements.

��管你可以调节很多MySQL服务器上的变量，但是在大多数通常的工作负载下�Q�只有少数几个才真正重要。如果你把这些变量设�|�正��了�Q�那么修改其他变量最多只能对�pȝ��性能改善有一定提升�?br />
key_buffer_size - Very important if you use MyISAM tables. Set up to 30-40% of available memory if you use MyISAM tables exclusively. Right size depends on amount of indexes, data size and workload - remember MyISAM uses OS cache to cache the data so you need to leave memory for it as well, and data can be much larger than indexes in many cases. Check however if all of key_buffer is used over time - it is not rare to see key_buffer being set to 4G while combined size of .MYI files is just 1GB. This would be just a waste. If you use few MyISAM tables you’ll want to keep it lower but still at least 16-32Mb so it is large enough to accommodate indexes for temporary tables which are created on disk.

key_buffer_size - �q�对MyISAM表来说非帔R��要。如果只是��用MyISAM表，可以把它讄��为可用内存的 30-40%。合理的值取决于索引大小、数据量以及(qi��ng)负蝲 -- ��C��Q�MyISAM表会(x��)使用操作�pȝ��的缓存来�~�存数据�Q�因此需要留出部分内存给它们�Q�很多情况下数据比烦(ch��)引大多了。尽��如此，需要��L��(g��)查是否所有的 key_buffer 都被利用�?-- .MYI 文�g只有 1GB�Q��?key_buffer 却设�|��ؓ(f��) 4GB 的情冉|��非常��的。这么做太浪费了。如果你很少使用MyISAM表，那么也保留低�?16-32MB �?key_buffer_size 以适应�l�予��盘的��(f��)时表索引所需�?br />
innodb_buffer_pool_size This is very important variable to tune if you’re using Innodb tables. Innodb tables are much more sensitive to buffer size compared to MyISAM. MyISAM may work kind of OK with default key_buffer_size even with large data set but it will crawl with default innodb_buffer_pool_size. Also Innodb buffer pool caches both data and index pages so you do not need to leave space for OS cache so values up to 70-80% of memory often make sense for Innodb only installations. Same rules as for key_buffer apply - if you have small data set and it is not going to grow dramatically do not oversize innodb_buffer_pool_size you might find better use for memory available.

innodb_buffer_pool_size - �q�对Innodb表来说非帔R��要。Innodb相比MyISAM表对�~�冲更�ؓ(f��)敏感。MyISAM可以在默认的 key_buffer_size 讄��下运行的可以�Q�然而Innodb在默认的 innodb_buffer_pool_size 讄��下却跟蜗牛似的。由于Innodb把数据和索引都缓存�v来，无需留给操作�pȝ��太多的内存，因此如果只需要用Innodb的话则可以设�|�它高达 70-80% 的可用内存。一些应用于 key_buffer 的规则有 -- 如果你的数据量不大，�q�且不会(x��)暴增�Q�那么无需�?innodb_buffer_pool_size 讄��的太大了�?br />
innodb_additional_pool_size This one does not really affect performance too much, at least on OS with decent memory allocators. Still you might want to have it 20MB (sometimes larger) so you can see how much memory Innodb allocates for misc needs.

innodb_additional_pool_size - �q�个选项�Ҏ(gu��)��能影响�q�不太多�Q�至��在有差不多��_��内存可分配的操作�pȝ��上是�q�样。不�q�如果你仍然惌��|��ؓ(f��) 20MB(或者更�?�Q�因此就需要看一下Innodb其他需要分配的内存有多��?br />
innodb_log_file_size Very important for write intensive workloads especially for large data sets. Larger sizes offer better performance but increase recovery times so be careful. I normally use values 64M-512M depending on server size.

innodb_log_file_size 在高写入负蝲��其是大数据集的情况下很重要。这个��D��大则性能相对��高�Q�但是要注意到可能会(x��)增加恢复旉��。我�l�常讄��?64-512MB�Q�跟据服务器大小而异�?br />
innodb_log_buffer_size Default for this one is kind of OK for many workloads with medium write load and shorter transactions. If you have update activity spikes however or work with blobs a lot you might want to increase it. Do not set it too high however as it would be waste of memory - it is flushed every 1 sec anyway so you do not need space for more than 1 sec worth of updates. 8MB-16MB are typically enough. Smaller installations should use smaller values.

innodb_log_buffer_size 默认的设�|�在中等强度写入负蝲以及(qi��ng)较短事务的情况下�Q�服务器性能�q�可以。如果存在更新操作峰值或者负载较大，��应该考虑加大它的��g��。如果它的��D��|�太高了�Q�可能会(x��)��费内存 -- 它每�U�都�?x��)刷��C��ơ，因此无需讄��过1�U�所需的内存空间。通常 8-16MB ��p��够了。越��的�pȝ��它的��D��?br />
innodb_flush_logs_at_trx_commit Crying about Innodb being 100 times slower than MyISAM ? You probably forgot to adjust this value. Default value of 1 will mean each update transaction commit (or each statement outside of transaction) will need to flush log to the disk which is rather expensive, especially if you do not have Battery backed up cache. Many applications, especially those moved from MyISAM tables are OK with value 2 which means do not flush log to the disk but only flush it to OS cache. The log is still flushed to the disk each second so you normally would not loose more than 1-2 sec worth of updates. Value 0 is a bit faster but is a bit less secure as you can lose transactions even in case MySQL Server crashes. Value 2 only cause data loss with full OS crash.

innodb_flush_logs_at_trx_commit 是否为Innodb比MyISAM�?000倍而头大？看来也许你忘了修改这个参��C��。默认值是 1�Q�这意味着每次提交的更��C��务（或者每个事务之外的语句�Q�都�?x��)刷新到��盘中，而这相当耗费资源�Q�尤其是没有甉|��备用�~�存时。很多应用程序，��其是从 MyISAM转变�q�来的那些，把它的��D��|��ؓ(f��) 2 ��可以了�Q�也��是不把日志��h��到磁盘上�Q�而只��h��到操作系�l�的�~�存上。日志仍然会(x��)每秒��h��到磁盘中去，因此通常不会(x��)丢失每秒1-2�ơ更新的消耗。如果设�|��ؓ(f��) 0 ��快很多了，不过也相对不安全�?-- MySQL服务器崩溃时��׃��(x��)丢失一些事务。设�|��ؓ(f��) 2 指挥丢失��h��到操作系�l�缓存的那部分事务�?br />
table_cache - Opening tables can be expensive. For example MyISAM tables mark MYI header to mark table as currently in use. You do not want this to happen so frequently and it is typically best to size your cache so it is large enough to keep most of your tables open. It uses some OS resources and some memory but for modern hardware it is typically not the problem. 1024 is good value for applications with couple hundreds tables (remember each connection needs its own entry) if you have many connections or many tables increase it larger. I’ve seen values over 100.000 used.

table_cache -- 打开一个表的开销可能很大。例如MyISAM把MYI文�g头标志该表正在��用中。你肯定不希望这�U�操作太频繁�Q�所以通常要加大缓存数量，使得��以最大限度地�~�存打开的表。它需要用到操作系�l�的资源以及(qi��ng)内存�Q�对当前的硬仉��|�来说当然不是什么问题了。如果你�?00多个表的话，那么讄��?1024 也许比较合适（每个�U�程都需要打开表）�Q�如果连接数比较大那么就加大它的倹{��我曄��见过讄��?100,000 的情��c(di��n)�?br />
thread_cache Thread creation/destructions can be expensive, which happen at each connect/disconnect. I normally set this value to at least 16. If application has large jumps in amount of concurrent connections and I see fast growth of
Threads_Created variable I boost it higher. The goal is not to have threads created in normal operation.

thread_cache -- �U�程的创建和销毁的开销可能很大�Q�因为每个线�E�的�q�接/断开都需要。我通常臛_��讄��?16。如果应用程序中有大量的跌��q�发�q�接�q�且 Threads_Created 的��g��比较大，那么我就�?x��)加大它的倹{��它的目的是在通常的操作中无需创徏新线�E��?br />
query_cache If your application is read intensive and you do not have application level caches this can be great help. Do not set it too large as it may slow things down as its maintenance may get expensive. Values from 32M to 512M normally make sense. Check it however after a while and see if it is well used. For certain workloads cache hit ratio is lower than would justify having it enabled.

query_cache -- 如果你的应用�E�序有大量读�Q�而且没有应用�E�序�U�别的缓存，那么�q�很有用。不要把它设�|�太大了�Q�因为想要维护它也需要不��开销�Q�这�?x��)导致MySQL变慢。通常讄��?32-512Mb。设�|�完之后最好是跟踪一�D�|��_(d��)��查看是否�q�行良好。在一定的负蝲压力下，如果�~�存命中率太低了�Q�就启用它�?br />
Note: as you can see all of these are global variables. These variables depend on hardware and mix of storage engines, while per session variables are typically workload specific. If you have simple queries there is no reason to increase sort_buffer_size even if you have 64GB of memory to waste. Furthermore doing so may decrease performance.
I normally leave per session variable tuning to second step after I can analyze workload.

注意�Q�就像你看到的上面这些全局表量�Q�它们都是依据硬仉��|�以�?qi��ng)不同的存储引擎而不同，但是�?x��)话变量通常是根据不同的负蝲来设定的。如果你只有一些简单的查询�Q�那么就无需增加 sort_buffer_size 的��g��Q�尽��你�?64GB 的内存。搞不好也许�?x��)降低性能�?br /> 我通常在分析系�l�负载后才来讄��?x��)话变量�?br />
P.S Note MySQL distribution contains bunch of sample my.cnf files which may be great templates to use. Typically they would already be much better than defaults if you chose correct one.

P.S�Q�MySQL的发行版已经包含了各�U?my.cnf 范例文�g了，可以作�ؓ(f��)配置模板使用。通常�q�比你��用默认设�|�好的多了�?/div>

becket_zheng 2010-03-30 17:00 发表评论

[集群]基础

becket_zheng — Tue, 30 Mar 2010 08:57:00 GMT

[集群]基础

1.��L(f��ng)��要什么是集群技术？��Z��么要使用集群技术？

集群是一�l�协同工作的服务实体�Q�用以提供比单一服务实体更具扩展性和可用�?/strong>的服务��^台�?/div>

2.误��Z��所知道的集��种�c�，和实现方案？

目前Linux下的集群主要有三�U�类�?nbsp;

1. HA (High Availability)

2. LB (Load Balancing)

3. HPC (High performance Computing)

�?DC (Distributed Computing)

�?PC (Parallel Computing)

高性能计算集群�Q�High Performance Compute clustering�Q�（�?Beowulf�Q��用多个机器来为需要大量计��能力的��d��提供更强大的计算能力。RHEL没有内嵌�q�类集群的解��x��案�?nbsp;

高可用性集��（High-availability clustering�Q��用多个机器来为某个服务或某组服务提供额外的可靠性�?nbsp;

负蝲均衡集群�Q�Load-balance clustering�Q��用特�D�的路由技术来�l�一�l�服务器分配��d��?nbsp;

RedHat提供了后两种集群技术的解决�Ҏ(gu��)��。��用一�l�程序来监视该系�l�和集群中的服务的健��L(f��ng)��c(di��n)�?/div>
虽然集群�pȝ��q�不能解��x��有的�pȝ��问题�Q�但是它能够帮助�pȝ��理员最大限度地利用现有的资源。�ƈ不是所有的�E�序都适用于集��系�l�，但是常见的系�l�应用如HTTP服务�Q�FTP服务�Q�数据库服务都可以利用集��系�l�来增强它们的功能�?/div>
3.什么时候需要用LB集群�Q?/div>

公共WEB服务、FTP服务、数据库服务�{�高负蝲服务中�?/div>

4.什么时候需要��用HA集群�Q?/div>

Ha集群主要用于文�g服务�Q�W(xu��)EB服务�Q�数据库服务�{�关键应用中

5.Linux下实现LB集群的项目是�Q?/div>

目前在LINUX�pȝ��下��用最为广泛的LB集群�pȝ��为LVS

becket_zheng 2010-03-30 16:57 发表评论

SQL注入相关

becket_zheng — Mon, 22 Mar 2010 01:01:00 GMT

来自千一�|�络

看了��竹的《SQL注入天书之ASP注入漏洞全接触》，感觉�q�篇文章写得非常好，由浅入深�Q�实例详��，�Ҏ(gu��)��手�v到教学作用，对老手起到交流探讨作用�Q�目前近40%的ASP�|�页均存在此漏洞�Q�可以说《SQL注入天书之ASP注入漏洞全接触》也来得非常实用�?/p>

我是从其它网站上拯��?#8220; 　　http://www.mytest.com/showdetail.asp?id=49 ;and (select count(*) from sysobjects)>0
　　修改为：(x��)
http://www.mytest.com/showdetail.asp?id=49 and (select count(*) from sysobjects)>0

SQL Server注入漏洞可能造成什么损失呢�Q?br /> 　　轻：(x��)查看数据库名、SQL Server�q�接名、得到表的字�D�与记录�{��?br /> 　　重：(x��)备䆾数据库、下载数据库、在计算机内��d��理员等�?/p>

“查看数据库名、SQL Server�q�接名、得到表的字�D�与记录”之类的攻击，对于存在注入漏洞的网��一般都可实现。但若是使用Web��理�|�站�Q�W(xu��)eb的密码又没加密，�q�样事态就变严重了。另外对于SELECT语句�Q�如果没有控制好LockType�Q�应讄��为adLockReadOnly�Q�，也是很严重的�?/p>

对于ASP�Q�SQL Server如何��d��防范注入漏洞�Q?/strong>
　　一、对�q�入sql语句的数字先�q�行�c�d��转换
　　二、对�q�入sql语句的字�W�，��单引号("'")替换��Z��个单引号("''")或其�?/p>

仅此两点卛_��Q�也许有��Z��(x��)问，那么文中�W?��|��_(d��)��(x��)

在入门篇提到�Q�有很多人喜�Ƣ用’��h��试注入漏�z�，所以也有很多�h用过�?#8217;��L(f��ng)��Ҏ(gu��)��?#8220;防止”注入漏洞�Q�这也许能挡住一些入门者的��d��Q�但对SQL注入比较熟�?zh��n)�的�h�Q�还是可以利用相关的函数�Q�达到绕�q�程序限制的目的�?/div> 　　是什么意思呢�Q�既然说�q�行�c�d��转换�Q�过滤掉"'"��可以了�Q�这里怎么又说可以�l�过"'"的限制呢�Q�其实，�q�里所说的是指�Ҏ(gu��)��字类型或我们注入��d��的sql。也��是��_(d��)��(x��)

对sql = "……where id=" & request.QueryString("id")
　　�?*.asp?id=char(50)�Q�char�?x��)�v到函数的作用

或者where xtype=char(85)�Q�见文中�W?��）�Q�char也会(x��)起到函数的作用�?/p>
但对于sql = "……where key='" & request.QueryString("key") & "'"
　　�?*.asp?key=char(50)�Q�这里的char(50)是不起作用的�Q��ؓ(f��)什么呢�Q?br /> 　　套入sql一看，语句是这��L(f��ng)��Q?br /> 　　sql = "……where key='char(50)'"
　　char(50)位于"'"内，变成了字�W�（�Ԍ��Q�所以就起不到函数的作用了�?/p>
��L��好的�?f��n)惯�Q�制定统一的规�?br /> 　　上面的方法确实解决了注入漏洞问题�Q�但�q�不表示其它地方可以马虎了，��Z��么要马虎了，��Z��么要让自��q��|�页千疮癑֭��Q�让几句代码�ȝ��挡一面呢�Q�如果不��L��好的�?f��n)惯�Q�团体之间如果不制定�l�一的规范，今天�q�个问题解决了，明天那个问题�q�会(x��)出现�?/p>
�Q�、��用RecordSet记录集之前必��d��断RecordSet的BOF或EOF属性�?br /> 　　�Q�、对于SELECT语句�Q�除了不得已的情况，LockType必须讄��为adLockReadOnly�?br /> 　　�Q�、放入数据库中的密码应该使用良好的加密算法进行加密，同时也禁止密码以明文的�Ş式存在于��面文�g中�?br /> 　　�Q�、在Web条�g下，在非本机调试的情况下�Q�不得��用sa�q�接数据库�?br /> 　　�Q�、对于需要用��h��限的�q�_��Q�必��d��用户名和密码载入session�Q�然后在需要的��面�q�行判断�Q�不得��用if session("loginOK")<>"" then之类的语句来判断用户是否是合法用戗��?br /> 　　……
　　必要�Ӟ��可以��止IIS�q�回详细的出错信息，可以��止public对sysobjects表的SELECT权限�?br /> 　　……

安全不是一斚w��的，仅靠几个规范几个好的�?f��n)惯�q�不能保证能造就出安全的�I�间�Q?个False�?9个True�q�行“�?#8221;�q�算�Q�结果还是False�Q�从中可以看出，哪怕只有一炚w��误，都可能导致结果全盘被否定。Web安全�Q�除了注入漏�z�，�q�有FTP讄��错误、Web服务讄��错误、后台程序漏�z�这些最最基本的都可能��D��服务器整个被人控�Ӟ��所以处处都要三思啊�?/p>
再次说明防注入不是替换关键字�Q?br />

最�q�又看到很多关于 SQL 注入的帖子，都是使用替换 select、delete、update �{�字�W�串的方法来防注入的�?/p>
再说明一下，�q�种是错误的防注入方法，原因如下�Q?/span>

可能替换不全�Q�不是所有的关键字都列入其中了的�?
本��n�q�种替换��有漏洞�Q�比�?aandnd 本��n没有问题�Q�把其中�?and 替换掉后�Q�反而冒��Z��?and 出来�?
�q�种替换方式�q�破坏了文字的原义，我曾�l�在某个�|�站上注册了 candy �q�个用户名，后来该系�l�却告诉我没有这个用��P��后来才知�?candy 中的 and 被去掉了�?/li>

正确的防注入�Ҏ(gu��)��是：(x��)

�Ҏ(gu��)��字类型进�?sql 前强制�{换�ؓ(f��)数字�?
�Ҏ(gu��)��本类型进�?sql 前替换单引号为双引号�?
�Ҏ(gu��)��期类型进�?sql 前强制�{换成日期�Q��ƈ替换单引号�ؓ(f��)双引受��?/li>

�q�是从注入的原理来防的�?/p>

becket_zheng 2010-03-22 09:01 发表评论

becket_zheng — Fri, 19 Mar 2010 01:24:00 GMT
今天下了个源�?�Q�结果在IIS中浏览出现错误：(x��)
今天遇到�q�个问题��试很多�Ҏ(gu��)��Q�最后看到这��文章，解决了！�Q?br />

    "服务器应用程序不可用" �(zh��n)�试囑֜��?Web 服务器上讉K��?Web 应用�E�序当前不可用。请点击 Web ��览器中�?#8220;��h��”按钮重试�(zh��n)�的��h��。管理员注意事项:详述此特定请求失败原因的错误信息可在 Web 服务器的�pȝ��事�g日志中找到�?br />     到日志去一查，发现�Q?#8220;aspnet_wp.exe (PID: 356)意外停止�?/font>” “�׃�� ASP.NET �q�程标识对全局�E�序集缓存没有读权限�Q�因此未能执行请求。错�? 0x80070005 拒绝讉K��?#8221;

    到网上找了很长时间看了很多的相关资料�Q�有说是微��Y补丁�Q�KB886093�Q�的问题�Q�但是我的机器根本就没安�q�个补丁�Q�有的说需要重新注册IIS�Q�有的说需要配�|�machine.config但是我有的项目是也是��览的，郁闷了好久，��试了很多办法，觉得问题可能是出在IIS的权限设�|�，所以又重新��IIS的权限设�|�了一�?具体做法�Q?/font>

    IIS中左键单击需要运行的Web站点->所有�Q�?>权限向导->�l�承所有安全性设�|?>完成.

    �l�果你猜怎么了，哈哈�Q�涛��C��旧啦�Q�！�Q?/font>

becket_zheng 2010-03-19 09:24 发表评论

becket_zheng — Mon, 01 Feb 2010 14:36:00 GMT

关于搜烦(ch��)优化的问题：(x��)
假设有个�|�站�Q�有主页 in,主页的链接l1,l2,l3.
目前�q�四个网��늚�搜烦(ch��)关键字都是：(x��)"A B C",如下�Q?br /> 都是一��L(f��ng)��?br /> 目前癑ֺ�搜烦(ch��)"A"�Q�排名第一�Q�搜索C�Q�排名非常的靠后�?/p>
现在惌��C也能在百度搜索里面靠前，所以打��这��P��(x��)
l2和l3��面分别�Ҏ(gu��)��q�样�Q?br />

�q�样的话�Q�是不是��可以了�Q�这样做�Q�会(x��)不会(x��)影响了A的搜索排名？

becket_zheng 2010-02-01 22:36 发表评论

探寻IIS最大�ƈ发数

becket_zheng — Tue, 19 Jan 2010 17:27:00 GMT

探寻IIS最大�ƈ发数

��试�pȝ��Window 2003 Server ,IIS 6.0 ,ASP.Net 3.5 sp1
Dual 1.8双核�Q?G内存�Q?4G虚拟内存�?/p>
��Z��探寻IIS的最大�ƈ发数�Q�先要做几个假设�?/p>
1、假设最大�ƈ发数��是当前的连接数。意思是当前能承受最大的�q�接�Q�那么就表明最大的�q�发�?br /> 2、假设IIS应用�E�序池处于默认状态，更改讄��会(x��)�Ҏ(gu��)��大连接数产生影响�?/p>
做完假设�Q�现在做限制�Q�设�|�站点保持HTTP�q�接�Q�超时设�|�成0�Q�就是不�?x��)超时。在站点��h��的default.aspx��面讄��U�程Thread.Sleep(int.MaxValue)�Q�接下来开发一个用来保持连接的��程序�?/p>
Code
    class Program {
        private volatile static int errorCount = 0;
        private volatile static int rightCount = 0;

        static void Main(string[] args) {
            ServicePointManager.DefaultConnectionLimit = 10000;
            int count = 0;
            int all = 0;
            while (true) {
                all++; count++;
                CreateThread();
                Thread.Sleep(10);
                if (count >= 200) {
                    Console.WriteLine(string.Format("sucess:{0};error:{1}", all - errorCount, errorCount));
                    count = 0;
                }
                if (all > 1800)
                    break;
            }
            Console.ReadKey();
        }

        static void CreateThread() {
            Thread thread = new Thread(ActiveRequest);
            thread.IsBackground = true;
            thread.Start();
        }

        static void ActiveRequest() {
            RequestClient client = new RequestClient("http://192.168.18.2/default.aspx?d=" + Guid.NewGuid());
            client.RequestProcess();
            if (client.IsError) {
                errorCount++;
                Console.WriteLine(string.Format("错误消息:{0}", client.Messages));
            } else {
                rightCount++;
                //Console.WriteLine(client.Messages);
            }
        }
    }

/**
* author : yurow
*      http://birdshover.cnblogs.com
* description:
*
* history : created by yurow 2009-8-16 0:29:05
*/

using System;
using System.Collections.Generic;
using System.Text;
using System.Net;
using System.IO;

namespace MaxLinked {
    ///

    ///
    ///

    public class RequestClient {
        HttpWebRequest request;
        WebResponse response;

        public RequestClient(string url) {
            request = (HttpWebRequest)HttpWebRequest.Create(url);
            request.Timeout = int.MaxValue;
            request.KeepAlive = true;
            ErrorCode = -1;
        }

        public void AddHeader(string name, string value) {
            request.Headers.Add(name, value);
        }

        private bool isError = false;
        private StringBuilder buffer = new StringBuilder();

        public int ErrorCode { get; set; }

        public bool IsError {
            get { return isError; }
        }

        public string Messages {
            get { return buffer.ToString(); }
        }

        public void RequestProcess() {
            try {
                response = request.GetResponse();
            } catch (WebException ex) {
                ErrorCode = (int)ex.Status;
                buffer.Append(ex.Message);
                isError = true;
            }
            if (response != null) {
                Stream stream = null;
                StreamReader reader = null;
                try {
                    //stream = response.GetResponseStream();
                    //reader = new StreamReader(stream, Encoding.UTF8);
                    //buffer.Append(reader.ReadToEnd());
                } catch (Exception ex) {
                    buffer.Append(ex.Message);
                    isError = true;
                } finally {
                    //if (reader != null)
                    //    reader.Close();
                    //if (stream != null)
                    //    stream.Close();
                }
            } else {
                isError = true;
                buffer.Append("建立�q�接��p�|�Q?/span>");
            }
        }

        public void Close() {
            if (response != null)
                response.Close();
            request.Abort();
        }
    }
}

�E�序讄��为只能启�?800个线�E�，�q�是�׃��.Net单进�E�最大线�E�数好像�?000个。因此，要测试最大�ƈ发数�Q�要需要同时开几个��试�q�程。把�pȝ��虚拟内存调到最大��|��U�程�q�多�?x��)急剧占用内存。现在开始测试�?/p>
打开web站点的性能计数器，把显�C�比例调�?万�?/p>
发现�?000个连接时�Q�IIS服务器崩溃（503错误�Q�，��L��了个澡，发现IIS服务器无法自�׃��复错误。又��试了几�ơ，发现最大�ƈ发值是8200个，但是一般到5000左右��׃��(x��)崩溃�Q�有时候甚臛_��?000个�?/p>
�?200个计��，一个用户开一个浏览器��览�|�页�Q�可能会(x��)占用2�?个连接（参考�?a id="homepage1_HomePageDays_DaysList_ctl00_DayItem_DayList_ctl00_TitleUrl" class="postTitle2" >IIS�q�接数实验——Web开发必�?/span> 》）,按两个计��，那么IIS默认情况下，最大�ƈ发数�?000个左叟�?/p>
打开应用�E�序池配�|�，把最大工作进�E�数调高�Q�默认�ؓ(f��)1�Q�，能有效提高最大连接数。我记得以前看过一��文章，讲的是调�?左右比较合适�?/p>

becket_zheng 2010-01-20 01:27 发表评论

亚洲人成网址在线观看 ,中文字幕无码精品亚洲资源网,国产精品日本亚洲777

MySQL服务器安装完之后如何调节性能

[集群]基础

SQL注入 相关

探寻IIS最大�ƈ发数

探寻IIS最大�ƈ发数

SQL注入相关