From e8454fd0eb8af01dbba627ed707a7a45103daf3d Mon Sep 17 00:00:00 2001 From: Michael Orlitzky Date: Tue, 8 Oct 2013 20:35:36 -0400 Subject: [PATCH] Add an example of using multiple threads for DNS lookups. --- doc/man1/hath.1 | 13 +++++++++++++ hath.cabal | 13 +++++++++++++ 2 files changed, 26 insertions(+) diff --git a/doc/man1/hath.1 b/doc/man1/hath.1 index b72896a..6e7a618 100644 --- a/doc/man1/hath.1 +++ b/doc/man1/hath.1 @@ -109,6 +109,19 @@ the given CIDRs. 198.41.0.7: .fi .P +The DNS lookups are usually the bottleneck for this mode, but we can +perform them in parallel. Simply pass the number of threads to the GHC +runtime on the command line; for example, the following will perform +25 lookups in parallel: +.P +.nf +.I $ hath reversed +RTS -N25 <<< \(dq198.41.0.4/24\(dq +198.41.0.4: a.root-servers.net. +198.41.0.5: +198.41.0.6: rs.internic.net. +\(pc\(pc\(pc +.fi +.P Each of the modes also supports a present-tense flavor; the following are equivalent to their counterparts: \fBregex\fR, \fBreduce\fR, \fBdupe\fR, \fBdiff\fR, \fBlist\fR, \fBreverse\fR. diff --git a/hath.cabal b/hath.cabal index e6f5395..8eb569f 100644 --- a/hath.cabal +++ b/hath.cabal @@ -93,6 +93,19 @@ description: 198.41.0.6: rs.internic.net. 198.41.0.7: @ + . + The DNS lookups are usually the bottleneck for this mode, but we can + perform them in parallel. Simply pass the number of threads to the + GHC runtime on the command line; for example, the following will + perform 25 lookups in parallel: + . + @ + hath reversed +RTS -N25 <<< \"198.41.0.4\/24\" + 198.41.0.4: a.root-servers.net. + 198.41.0.5: + 198.41.0.6: rs.internic.net. + ... + @ executable hath build-depends: -- 2.43.2