[Tfug] Linux kernel tcp delay options 4e7uzube

Bexley Hall bexley401 at yahoo.com
Thu Jun 6 14:49:03 MST 2013


Hi Adrian,

> Yep, the best option would be for the app to use TCP_NODELAY when opening its
> socket... but alas Cyrus doesn;t do this, at least not in the CentOS 5.x
> package I have. There are lots of threads about this and dev comments that
> Cyrus should do this from several years back... but it apparently didn;t get
> in (which really suprises me that no one has fixed this in the last 10 years
> since I last used Cyrus).

Is there a counterargument as to why it "shouldn't"?  I.e., perhaps
<someone> intended it for use in a type of application where this
would be counterproductive?  Though one can argue for a configurable
option -- perhaps even "client/account specific"!  (Having a *core*
RDBMS service running in an OS should be a key requirement for any
OS "heavy" enough to support it!  Shame that this hasn't been the
case to date!)

> I may try pulling the source or package from a later CentOS version, but Cyrus
> is such a pain in the butt to get running in the first place... I didn;t want
> to end up breaking everything Ive got working.

Yup... the beauty of FOSS is that it lets *you* break the code
in whichever way(s) you see fit!  :<

G'luck!
--don




More information about the tfug mailing list