Never mind that question. Nginx uses domain sockets.by Ameisen - How to...
Unfortunately, I haven't yet had a chance to test this - I've been busy. However, a thought occurred - if one were to use Unix file streams instead of sockets, how would you use multiple connections? Would the load balancing approach be the only way?... as they're not as flexible as POSIX sockets.by Ameisen - How to...
With keepalive sockets, what should be expecting on the backend side? I presume what I will see is that every time a new concurrent connection is being made, a new transaction socket will be made, and at the end I will have <= 250 sockets that are just 'around' as they've been kept alive, and I will need to continue to put them on a recv?by Ameisen - How to...
I'm a bit confused again. "but as soon as you have to proxy-pass anything the backend can be blocking if it can't process multiple requests over the same connection" My backend (my FastCGI application) doesn't really block. It accepts connections on the listener socket, and defers them to other threads to process (which do so using a fiber pool) while the listener thread keeps listby Ameisen - How to...
All right, thank you. I'll try this tonight. What is nginx doing internally if I don't do this? IIRC, it defaults to 1 worker process, and that defaults to something like 512 connections? If 100 people connect and all are doing something that needs to talk to my FastCGI application, is it processing them all sequentially?by Ameisen - How to...
So, the config file (roughly), coupled with one instance of nginx and one instance of my application (which has concurrent socket capabilities) will suffice? Would it potentially make sense to just add an alias as something like fastcgi_concurrentsockets or somesuch? I absolutely don't want multiple instances of my application running. It's not designed for multiprocess safety, only multithread.by Ameisen - How to...
I wasn't aware that it wasn't supported, as I've been unable to find clear documentation anywhere about it. The only thing that I knew was unsupported was FastCGI multiplexing, but the argument given in the newsgroups for why it wasn't (aside from PHP not supporting it) was that equivalent functionality could be gotten by nginx opening multiple sockets, so I presumed that that was supported - theby Ameisen - How to...
I'm not using Lua, so using Lua APIs won't help me much. What I am presently doing is listening for connections on the socket. When a connection is found (which will be nginx) I accept the socket, and push the new transaction socket to a fiber-based job queue which executes it and responds when it has time. Immediately after pushing off the job, the listener socket goes back to listening. Both ngby Ameisen - How to...
The issue I'm seeing is that nginx never tries to open multiple sockets with the FastCGI application - I _am_ using coroutines with sockets - however, I never get more than one connection from the server at a time.by Ameisen - How to...
Hi there! I'm writing an application that is using fastcgi coupled with nginx. I have currently set it to use keepalive sockets. The application is designed so that any requests that come through are pushed onto an asynchronous queue and processed by multiple threads. However, I am not seeing behavior from nginx that is compatible with this - it appears as though it sends a request and doesby Ameisen - How to...
![]() |
![]() |
![]() |
![]() |
|