pconnect vs connect

perryp5

😕 ok i am having a problem with the pconnect function. On my database connections i have had to remove the pconnect and put connect instead. With pconnect i get a 'cant connect to database' message. with connect i do not have this problem. Any ideas??

Thanks,
Perry

Sxooter

Your apache server (I'm assuming you're running apache here, but it would be the same for any other server with different names) is set to handle more connections than your database server.

Generally, pconnects are not a good idea, since they don't scale well, as keeping lots of backend connections open and idle tends to eat up memory and such that other processes could be using.

If you're running apache, look for the line in the httpd.conf file that says:

MaxClients 150

and change it to a lower number (lower than the max connects your database is set to handle) and restart apache.

perryp5

Thank you for your reply. My server doesnt give me access to the httpd.conf file. hmmmm... I am perplexed Any suggestions on how to keep sessions open from page to page?

Thanks again,
Perry

perryp5

Thank you for your reply. My server doesnt give me access to the httpd.conf file. hmmmm... I am perplexed

Sxooter

If you can't access those parts of your server, you are better off using plain old connects.

There is VERY little gain from persistant connections for most scripts, and only the most heavily loaded servers stand to gain any real benefit.

the problem is that PHP doesn't really do what you need, which is real connection pooling. the persistant connections are per backend and only get reused when that particular backend reconnects.

Is your site running slowly or anything like that, or are you just trying to go for optimal performance?

perryp5

To be honest I am a newbie to PHP and am trying to complete the PHP Membership System 2.0 tutorial. I am building (have built) a site for my local AA central office. We will be adding an online store for our 'propaganda' :p I want to make a login system to give some of the bosses of the office access to some portions of the site. I really appreciate any help you give me.

http://www.aacentraloffice.us

thats the website.

Thanks again,
Perry

Sxooter

Oh, then just drop the pconnect until such time as you encounter enough load to justify switching to a bigger server / different host etc...

I.e. it's just a train wreck looking for a nice place to jump off the tracks right now. :-P

perryp5

Thanks again for your reply. So the session will stay open from page to page as long as it says session start at the top of the page right?

Thanks D00d,

Perry 😃

Sxooter

Right, sessions in PHP are not handled by the database, they are stored in the /tmp directory on a default install. So, no need for pg_pconnect for start_session type stuff.

Now, database connections, they will be brand spanking new every time you reload the page, but connection to mysql is REAL low (like <1mS, and even postgresql connects in <6 mS). Since the average page takes dozens to hundreds of mS to be built and delivered by comparison, the connect time is "no big deal" (TM etc... 🙂

perryp5

😃 k00l d00l Thank you so very much for the n00bie 101 help.