[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2813: -------------------------------------- There is a small discussion of this at https://community.jboss.org/thread/236413 I want to know the accumulated CPU from the translator's execute() and next() calls. I agree that nearly all translators are IO bound but some of our translators take on non-trivial CPU work to re-orient data that comes out of the source. In order to better direct our tuning efforts, having CPU time reported against the translator is useful. Ideally, Teiid would also report the total CPU required to process a user query so we can make query tuning decisions and, perhaps, supports* decisions. It is possible that even though a source can handle filtering, Teiid may be able to process the filter more efficiently - we have some very odd data sources. At this time, we don't *need* CPU time at the user-query level so this JIRA only addresses the translator. I was planning on reviewing the code to see how difficult it would be to add instrumentation at the higher level -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira