blob eec2c86b529d209f12a2ec6094c119a2b491cffc 3717 bytes (raw)
name: README # note: path name is non-authoritative(*)
= raindrops - real-time stats for preforking Rack servers
raindrops is a real-time stats toolkit to show statistics for Rack HTTP
servers. It is designed for preforking servers such as unicorn, but
should support any Rack HTTP server on platforms supporting POSIX shared
memory. It may also be used as a generic scoreboard for sharing atomic
counters across multiple processes.
* counters are shared across all forked children and lock-free
* counters are kept on separate cache lines to reduce contention under SMP
* may expose server statistics as a Rack Middleware endpoint
* middleware displays the number of actively processing and writing
clients from a single request regardless of which worker process
== Linux-only Extra Features!
* Middleware response includes extra stats for bound TCP and
Unix domain sockets (configurable, it can include stats from
other TCP or UNIX domain socket servers).
* TCP socket stats use efficient inet_diag facilities via netlink
instead of parsing /proc/net/tcp to minimize overhead.
This was fun to discover and write.
* TCP_Info reporting may be used to check stat for every accepted client
on TCP servers
Users of older Linux kernels need to ensure that the the "inet_diag"
and "tcp_diag" kernel modules are loaded as they do not autoload correctly
We recommend GCC 4+ (or compatible) to support the __sync builtins
For non-GCC 4+ users, we also support compilation with the libatomic_ops
package starting with Raindrops 0.4.0:
If you're using a packaged Ruby distribution, make sure you have a C
compiler and the matching Ruby development libraries and headers.
If you use RubyGems:
gem install raindrops
See Raindrops::Middleware and Raindrops::LastDataRecv documentation for
use Rack servers. The entire library is fully-documented and we are
responsive on the publicly archived mailbox
(mailto:email@example.com) if you have any questions or comments.
You can get the latest source via git from the following locations:
http://repo.or.cz/w/raindrops.git (gitweb mirror)
Snapshots and tarballs are available.
Inline patches (from "git format-patch") to the mailbox are
preferred because they allow code review and comments in the reply to
We will adhere to mostly the same conventions for patch submissions as
git itself. See the Documentation/SubmittingPatches document
distributed with git on on patch submission guidelines to follow. Just
don't email the git mailing list or maintainer with raindrops patches.
raindrops is licensed under the LGPL-2.1+
All feedback (bug reports, user/development discussion, patches, pull
requests) go to the publicly archived mailbox:
Mail archives are available over HTTP(S), IMAP(S) and NNTP(S):
Since archives are public, scrub sensitive information and
use anonymity tools such as Tor or Mixmaster if you deem necessary.
solving eec2c86 ...
found eec2c86 in https://yhbt.net/raindrops.git/
(*) Git path names are given by the tree(s) the blob belongs to.
Blobs themselves have no identifier aside from the hash of its contents.^
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).