[
https://issues.apache.org/jira/browse/NUTCH-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712492#action_12712492
]
Otis Gospodnetic commented on NUTCH-721:
----------------------------------------
Questions:
Has anyone tried profiling this? (may be relevant:
http://markmail.org/message/4ixrnvfycpgmkdno )
Or maybe simply debugged/timed various blocks of code using something as simple
as print statements and simple timers?
Or maybe running just a single thread and then doing kill -QUIT a number of
times to simply try and spot the method where the code seems to spend a lot of
its time?
> Fetcher2 Slow
> -------------
>
> Key: NUTCH-721
> URL: https://issues.apache.org/jira/browse/NUTCH-721
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Environment: Fedora Core r6, Kernel 2.6.22-14, jdk1.6.0_12
> Reporter: Roger Dunk
> Attachments: crawl_generate.tar.gz, nutch-site.xml
>
>
> Fetcher2 fetches far more slowly than Fetcher1.
> Config options:
> fetcher.threads.fetch = 80
> fetcher.threads.per.host = 80
> fetcher.server.delay = 0
> generate.max.per.host = 1
> With a queue size of ~40,000, the result is:
> activeThreads=80, spinWaiting=79, fetchQueues.totalSize=0
> with maybe a download of 1 page per second.
> Runing with -noParse makes little difference.
> CPU load average is around 0.2. With Fetcher1 CPU load is around 2.0 - 3.0
> Hosts already cached by local caching NS appear to download quickly upon a
> re-fetch, so possible issue relating to NS lookups, however all things being
> equal Fetcher1 runs fast without pre-caching hosts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
