Hi Willy, On 19:28 Fri 25 Jul , Willy Tarreau wrote: > > Concerning the new features, no promises, but we know that we need to > progress in the following areas : > > - multi-process : better synchronization of stats and health checks, > and find a way to support peers in this mode. I'm still thinking a > lot that due to the arrival of latency monsters that are SSL and > compression, we could benefit from having a thread-based architecture > so that we could migrate tasks to another CPU when they're going to > take a lot of time. The issue I'm seeing with threads is that > currently the code is highly dependent on being alone to modify any > data. Eg: a server state is consistent between entering and leaving > a health check function. We don't want to start adding huge mutexes > everywhere.
How about using shared memory segments for stats, health checks and peers? > > If anyone has any comment / question / suggestion, as usual feel free to > keep the discussion going on. Could I also add shared SSL session cache over multiple boxes (like stud), to aid SSL scalability behind LVS directors? It has been asked for before in the mailing list if I recall correctly. > For now enough talking, I'm going back to real work :-) Thanks again for the code :-) Regards, Apollon
