Re: Post data - Apache - FastCGI
Tim Wood <timwood0-yBeKhBN/[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <5.2.1.1.1.20050729150214.021fce10@mailhost> |
At 04:05 PM 07/29/05, you wrote: >...I have Apache web server with mod_fastcgi module and underlying program. >Now, that program is intended to be working with both GET and POST data. >However, due to the specifics of it, only 1 process is allowed. That's a pretty bad design decision if you care about performance. I would look at those specifics again. If you don't have some kind of concurrent connection handling, all your transactions will be serialized (obviously). >If we are uploading large amount of data using POST method, what is actually >happening? >Is apache buffering the data before sending it to the fastcgi process? If >that's so, the process get's "locked" while information from the client is >received - if the sender has bad internet connection, uploading 1mb would >take a long time - so, if fastcgi is waiting while data are coming and if >maxprocesses = 1, we have a problem.. Even if there's no buffering, you have a problem. Your system throughput is bounded by the connection speed of whoever's logged on, because the one fcgi is bound to that client. If a single fcgi process is some kind of checkoff item, the only thing I can think of is to use an external FCGI server that uses threads instead of processes. HTH, TW ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/