Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Profiling our topology I noticed that the DRPCSpout actually sleeps twice if it has nothing to do. This is due to a Utils.sleep(1) call at the end of nextTuple() while the SleepSpoutWaitStrategy performs the default sleep if a spout did not emit any tuple.
This causes - in my understanding - unnecessary context switches, especially with a high number of parallelism.
Attached the corresponding YourKit screenshot.
Attachments
Attachments
Issue Links
- links to