jnioche commented on PR #2261: URL: https://github.com/apache/stormcrawler/pull/2261#issuecomment-6410022429
> One useful approach would be to run the `StatusUpdaterBenchmark` with different cluster configurations x parameter values, then include the results directly in the documentation. This would give users a practical reference to help them find the optimal configuration for their setup. @GGraziadei the StatusUpdaterBenchmark simulates the activity of a crawl topology but is not a topology itself. The impact of batching should be measured with a proper crawl topology, maybe the one generated by the archetype and using URLFrontier? Given that most of a tuple's life is spent waiting in the FetchBolt for politeness reasons, I am not sure that batching would have any noticeable effect, positive or negative. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
