[pygccxml-development] Current status on additional caching support

[Allen B. <al...@vr...>]

I have been out of the loop for a couple of months and I was wondering 
what the current status on supporting additional caching with py++ is.

I know that Matthias had proposed some ideas in October that would 
minimize the number of symbols pulled in from gccxml.  What ever 
happened with that effort?  Are you still using it Matthias?

I had tried to increase performance by caching the decl parsing and 
query optimization run in module_builder.init().  This worked very well 
for me and I have code in goodie_perf_overrides.py that worked last time 
I tried, but alas this code seems to have broken since the last time I 
used it.  My guess is that module builder is now changed.

Roman: Is this idea of caching additional parts of the module builder 
initialization something you are interested in integrating into Py++?  
Atleast for me it had a significant impact on performance and made Py++ 
much more usable.

Are there any other optimizations floating around?  If you can't tell 
already I am pretty focused on performance on Py++.  In our workflow we 
do a lot of iterative development and any tool that runs slow can grind 
development progress to a halt.

Anyway, I just wanted to check in and see what is new that I should be 
looking into.

Thanks,
Allen