Re: buffering large input and output
"Xuefer" <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
"Marc Prewitt" <[email protected]> ??????:[email protected] > > Bryan White wrote: > >> Marc Prewitt wrote: >> >>> Here are the ones you need to set for this: >>> >>> FCGI_SERVER_MAX_STDERR_LINE_LEN (ours is 8192) >>> SERVER_BUFSIZE (ours is 65536) >>> >>> SERVER_BUFSIZE is used for an ap_pcalloc which is an int. That would >>> limit it to 65536. >> >> >> On what architecture that supports Apache and FastCGI is an integer a 16 >> bit value? >> > > My bad. Should have said, check your int size for max. However, > realize that this will cause mod_fastcgi to allocate this much memory > per connection. So, you want to make it something reasonable. all cgi process is waiting to send response, because mod_fastcgi don't recieve until it send some to client. isn't it reasonable? even use "tmpfile" to buffer if no more memory is better than all process hanging. and i wonder what will happened when many user is uploading BIG file slowly at the same time. > -------------------------------------------------------------------------------- ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/ ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/