Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Scott Marlowe
On Wed, 2006-03-29 at 16:48, Antimon wrote: > Yes i tried and realized apache child processes.. > Then i looked for another pooling solution, the project pgpool i found. > No windows binaries, it might run on cygwin. > After all, i think postgreSQL is not meant to run on windows production > for ~2

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Antimon
Yes i tried and realized apache child processes.. Then i looked for another pooling solution, the project pgpool i found. No windows binaries, it might run on cygwin. After all, i think postgreSQL is not meant to run on windows production for ~2 more major releases or something. It performs great o

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Scott Marlowe
On Wed, 2006-03-29 at 15:58, Scott Marlowe wrote: > On Wed, 2006-03-29 at 15:22, Antimon wrote: > > Just tried, yes, pconnect boosts multi user performance. > > But causes this: > > http://img526.imageshack.us/img526/6302/pgsql7th.jpg > > :) > > > > Need to modify max persistent connection setting

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Scott Marlowe
On Wed, 2006-03-29 at 15:22, Antimon wrote: > Just tried, yes, pconnect boosts multi user performance. > But causes this: > http://img526.imageshack.us/img526/6302/pgsql7th.jpg > :) > > Need to modify max persistent connection settings. I don't thin that doesn't do what you think it does. max pe

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Antimon
Just tried, yes, pconnect boosts multi user performance. But causes this: http://img526.imageshack.us/img526/6302/pgsql7th.jpg :) Need to modify max persistent connection settings. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ?

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Joshua D. Drake
Antimon wrote: Just noticed, On windows, these results are produced. But on linux, postgresql performs great. So postgre has a bad windows integration than mysql. Well since it supports win32 for a long time, it makes sense. I did some "multi client" tests and postgre could not even catch mysql s

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Antimon
Just noticed, On windows, these results are produced. But on linux, postgresql performs great. So postgre has a bad windows integration than mysql. Well since it supports win32 for a long time, it makes sense. I did some "multi client" tests and postgre could not even catch mysql so i decided to go

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Scott Marlowe
On Wed, 2006-03-29 at 12:19, Antimon wrote: > Hi, > I'm sorry about being understood like i was trying to compare pgsql > with mysql. I was trying stuff, did this and saw that huge difference > (even it is not bad alone, but comparing to mysql), and thought that > might be some library issue causin

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Antimon
Hi, I'm sorry about being understood like i was trying to compare pgsql with mysql. I was trying stuff, did this and saw that huge difference (even it is not bad alone, but comparing to mysql), and thought that might be some library issue causing slow reads from server. I don't need any rdbms to be

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Scott Marlowe
On Wed, 2006-03-29 at 02:45, Antimon wrote: > I know this is not even a test but i thought it might be a client > library issue, not server itself. > Well it is not, i tried it on .net with npgsql which is a .net client > library (Not using libpq). Results are same. Connect time does not have > muc

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Merlin Moncure
On 28 Mar 2006 17:01:45 -0800, Antimon <[EMAIL PROTECTED]> wrote: > Nearly 3 times slower even w/o any table queries. But i could not > reproduce this by writing stored procs on both which selects 0-1 in > a loop to a variable. results were almost same. > (I tried pg_ and mysqli_ functions too,

Re: [GENERAL] PostgreSQL client api

2006-03-29 Thread Antimon
I know this is not even a test but i thought it might be a client library issue, not server itself. Well it is not, i tried it on .net with npgsql which is a .net client library (Not using libpq). Results are same. Connect time does not have much effect by the way. ---(end

Re: [GENERAL] PostgreSQL client api

2006-03-28 Thread Scott Marlowe
On Tue, 2006-03-28 at 19:01, Antimon wrote: > Hi, > I was testing MySQL and PgSQL performances on my home box (amd athlon > 64 3000, 1gig ddr ram, sata I hdd, win xp (x86)), select and insert > times seeemed identical with innoDB. > > But when i try to query both using php, there's a huge differen

Re: [GENERAL] PostgreSQL client api

2006-03-28 Thread paul rivers
timon Sent: Tuesday, March 28, 2006 5:02 PM To: pgsql-general@postgresql.org Subject: [GENERAL] PostgreSQL client api Hi, I was testing MySQL and PgSQL performances on my home box (amd athlon 64 3000, 1gig ddr ram, sata I hdd, win xp (x86)), select and insert times seeemed identical with innoDB.

Re: [GENERAL] PostgreSQL client api

2006-03-28 Thread Jim C. Nasby
On Tue, Mar 28, 2006 at 05:01:45PM -0800, Antimon wrote: > $pdo = new PDO('pgsql:host=localhost;dbname=test', "testacc", "pw"); > for ($i = 0; $i < 1; $i++) > { > $result = $pdo->query("Select "+$i); > } > output is: > 2.7696590423584 Ok, so that tells me that on this plain-vanilla hardw

[GENERAL] PostgreSQL client api

2006-03-28 Thread Antimon
Hi, I was testing MySQL and PgSQL performances on my home box (amd athlon 64 3000, 1gig ddr ram, sata I hdd, win xp (x86)), select and insert times seeemed identical with innoDB. But when i try to query both using php, there's a huge difference even for a funny query like "select 1" Here's the co