Re: Connections per second?

I think it's simply impossible to have a persistent connection with CGI since the program is called and exited for each HTTP request (or am I wrong ?).
The only way to do that is either to develop an Apache module (sounds like reinventing the wheel to me), or using mod_perl or mod_php and the simple "ready to use" interfaces they provide.
In fact, it depends on how heavy your "must be fast" program will be to decide wether making it work as a CGI will introduce a big overhead relatively to the execution time or not. The longer the execution time will be, the more the CGI way will tend not to reduce performance.
That's my point of view, hope it helps
Arnaud

----- Original Message -----
From: "Alejandro Fernandez" <ale(at)e-group(dot)org>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, April 23, 2002 5:12 PM
Subject: [GENERAL] Connections per second?

Hi,

I'm writing a small but must-be-fast cgi program that for each hit it gets, it reads an indexed table in a postgres database and writes a log to a file based on the result. Any idea how many hits a second I can get to before things start crashing, or queuing up too much, etc? And will postgres be one of the first to fall? Do any of you think it can handle 2000 hits a second (what I think I could get at peak times) - and what would it need to do so? Persistent connections? Are there any examples or old threads on writing a similar program in C with libpq?

Thanks,

Ale

--
Alejandro Fernandez
Electronic Group Interactive
--+34-65-232-8086--

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly