14.02.2014 Views

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Buffer Stuffing<br />

(Single Threaded Installations Only)<br />

On single threaded installations the DSA can (obviously) only process a single<br />

request at a time. If a client submits a query that results in a large result set<br />

and then abandons the connection or goes off-net the server will remain tied<br />

up until the timelimit has expired. Such a course of events can also cause the<br />

server to experience intermittant load spikes.<br />

In an attempt to avoid this form of congestion slapd will request a large send<br />

buffer from the operating system. A large send buffer allows the server to<br />

dump the result set into the kernel and return to operation. It becomes the<br />

responsibility of the kernel to manage the defunct client connection.<br />

In order for this workaround to function properly the server administrator must<br />

usually raise the system's default maximum send buffer size. On Linux<br />

systems this can be adjusted with the following command:<br />

sysctl -w net.core.wmem_max = 4194<strong>30</strong>4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!