mysql_connect, mysql_pconnect... ideas ?

[Anon]

Ok this is the situation,

I'll have cpu and memory,
so dual PIII 1000 MHZ and at least 512 MB of ram but I still can't decide or ... perhaps understant the implications of mysql_connect and mysql_pconnect.

I've gone through some of the threads in this forum and ppl say connect saves memory and p_connect saves cpu... well in my case that does not chage anything... with what I have I can use both.

BUT!, I want to make sure that I'm taking the right decision because later on ... it will be difficult for me to ... rollback 🙂

I'm guessing here that the mysql server will have about 1 000 000 hits/querys a day all selects... the updates are very small.

in a sitation like this would it be preferable to use pconnect or just connect ?

everything is db driven and the user might stay online for ... 60 minutes so I'm guesing that a p_connect will not do the job because of the connection/thread limit ?!

one more thing, let's say I start a pconnect in index.php page. should I also do pconnect again in ... main.php or I can just run my mysql_query right away ignoring the pconnect because I've already done it one in index.php ?

thanks alot
I'll appreciate any feedbacks!!

best regards,
Patrick.

[Anon]

If you're running so many queries, connecting and dicsonnecting millions of times seems a waste, so pconnect is probably the best bet. You'd replace ALL your mysql_connect statements with mysql_pconnect, and it'd just use the same connection rather than connect/disconnect all day.