Optimize the way expressions and cursor are resolved in the context

Description

There are some queries (e.g., slowcomp8) which spend a large proportion of their time resolving expressions and cursors in the current context. There are a couple of relatively simple improvements:

  • use the hash table more of the time. It is only problematic if a cursor is added that was already in scope

  • limit the search range in the expressions.

The second could be done by having separate arrays for the different types, but the short term fix is to save the index of the last cursor, to avoid in the common case searching large numbers of expressions.

Conclusion

None

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Labels

Created March 21, 2017 at 12:46 PM
Updated June 1, 2017 at 2:18 PM
Resolved March 24, 2017 at 9:01 AM