I will register my idea, which requires more work. Expose a metric port, which can be aggregated at another operator. Default operator could be AppDataPushAgent operator. Users can plugin their own operators to send the metric to different types of sinks.
On Tue, Mar 14, 2017 at 11:17 PM Chinmay Kolhatkar <chin...@apache.org> wrote: > Dear Community, > > While going through the code, I found that the AutoMetrics are retrieved > from operators using java reflection. This adds a lot of processing > overhead. > > Hence to improve the performance of containers and stram, I want to suggest > following appraoch: > 1. In Node, try to collect the metric using getter method using Janino if > available, if not fallback to reflection. > 2. In operator documentation, suggest to have a getter method/public for > autometrics. > 3. In AppDataPushAgent, use Janino to get the AutoMetrics present in > LogicalOperatorInfo > > Please share your opinion. > > Thanks, > Chinmay. > -- *Join us at Apex Big Data World-San Jose <http://www.apexbigdata.com/san-jose.html>, April 4, 2017!* [image: http://www.apexbigdata.com/san-jose-register.html]