Well,

After I wrote the email and begin to test it.
First,its cool.I really could feel the speed up after use persistent mysql
connection,you will feel the delay when system create the database
connection there,almost 1~2 secs I think.(I use 56K dialup).once
established,its so fast!

Second.If Turn KeepAlive Off.well,its funny.I feel the delay again!but  I
found out the reason is not cost on database connection,but startup a new
Apache child!,almost same as create database connection,but worse I think.
So why slashdot.org turn it off?must be some,eh?Any other developer here
experience this one?

Also,more interest thing is that,when Turn it off and I exam with
"mysqladmin processlist".It's funny that though apache regenerate a new
child but  this child just pick up a exist mysql connection  RANDOMLY from
all exist connection,so smart?Does the parent apache transfer some info to
it otherwise how come it know those exist one?I think Apache::DBI just will
check the database connection create by the child serve the script,now seems
Apache::DBI check in the parent Apache process?


Any idea?

______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com?sr=mc.mk.mcm.tag001

Reply via email to