Threading

Loghub uses threads transparently to do parallel processing and don't lock.

For developpement it's should me transparent, but anyway some precautions must be used and the threading model must be understood to fully reach Loghub's performance goals.

Input

Input object are mono threaded as usually they listen on a single network port that will be difficult to share. The developper must then take care of blocking code.

Output

Processors

Each processor step in a pipeline exists as a single instance that will be shared by all the workers thread. If a processor class is used in different pipeline steps, they will be different instances.

As a processor is generally stateless, that should not be a problem. But if some non thread safe object are to be used, extra care must be used, a java.lang.ThreadLocal is a very efficient solution to this problem.