detailed timing of various compiler phases

Bug #867302 reported by Matthias Brantner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zorba
New
Medium
dan-muresan

Bug Description

Could we provide timing information for each compiler phase (i.e. parser, normalizer, optimizer, codegen)?

Revision history for this message
Vinayak R. Borkar (vinayakb) wrote :

Is this still pending?

Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

Yes, this is still something very useful and has not been done.

Revision history for this message
Vinayak R. Borkar (vinayakb) wrote :

Dan,

Can you take care of this?

Revision history for this message
dan-muresan (dan-muresan) wrote :

Yes, this is still pending. There are a number of things hampering this:

1. (design) where to store the timers -- each timer needs to subsume timers for the modules and UDFs invoked from the current query recursively. Easiest would be global timers accessed via System::properties, but that incurs the synchronization cost and will still not work with multi-threading

1. zorbacmd is supposed to limit itself to the public API. Thus, the above timers need to be visible via the API, or we need to break the rules yet again.

Chris Hillery (ceejatec)
tags: removed: command-line-client
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.