Apple

On 19.10.2009, at 20:09, Jens Alfke wrote:

On Oct 19, 2009, at 10:54 AM, Andreas Fink wrote:

I have a project where our software would have to act as a modified HTTP proxy with transcoding and conversion functionality built in. I'm not too concerned about the CPU load right now as we can spread the load among multiple machines but it would then require a load balancer which has the same limits as below.

I'm not an expert here, but I believe round-robin DNS is often used for this. That multiplexes the load across several servers, and only the DNS server (which is UDP-based) needs to handle the full number of requests.

Thats not an option here as the calling device has an IP address configured in 99% of the cases, not a DNS name.

Can anyone shed a light on what those soft/hard limits in the current MacOS X Server implementations are and how to change them by sysctl or by recompilation of kernel or if would be smarter to use Linux for that?

You can't modify the kernel on OS X. That is, you could check out Darwin and build a kernel from that, but AFAIK it isn't feasible to splice such a modified kernel into an OS X installation.

I'll probably better ask this on the kernel mailing list. Recompiling the kernel for this scenario is ok.
A sysctl would be better though.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>TCP limits (From: Andreas Fink <email@hidden>)
	>Re: TCP limits (From: Jens Alfke <email@hidden>)
	>Re: TCP limits (From: Andreas Fink <email@hidden>)