Johan Haleby wrote:
The heap size doesn't increase until the data-producing device is shutdown,
it fluctuates like it should do (after tweaking the GC).
The CPU usage goes
up dangerously close to 100% pretty fast though.
This would seem to indicate that the amount of data buffered does not
increase with time, ie. you can handle all the traffic produced by the
device. What happens if do whatever transformations you do to the data,
and then simply discard it instead of writing it to the recipient
sessions? Can you try replacing reading from the device with some dummy
data source with the goal of not using as much resources as actual
reading, and thus potentially being able to find the bottleneck?
