| RE: [cdt-dev] Firefox Fast Index Times |
|
Unfortunately, no. J I started using the TPTP profiler to test
out our old parser performance test we affectionally cursed, the Trilogy. The
Trilogy is a simple file that looks a lot like this: #include <stdio.h> #include <iostream> int main() { return 0; } We used to run it with cygwin with the
mingw package installed (to get windows.h). I am now doing it with the Windows
Build integration. With my first run, I am seeing
FindEquivalentBinding visitor taking 2/3’s of the time. This visitor is new and
searches the PDOM very often. I can see how, as the PDOM gets bigger, this
function takes a bit longer since the searches have a bigger B-Tree to deal
with (but theoretically, the incremental time should be minimal). But this
functionality is new in HEAD and should be a good place to start. Cheers, Doug Schaefer, QNX Software Systems From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin I guess the difference in
indexing time reflects the improvement in index coverage :-). On 11/17/06, Doug
Schaefer <DSchaefer@xxxxxxx>
wrote: Hey
gang, We've
now cleared up enough exceptions to fully index Firefox 2.0 with the Fast
indexer. Here are the numbers I got. The initial index is the first one after
launching Eclipse (includes binary parser times, disk caching, etc.) and the
reindex is from the Reindex menu item (pretty much pure indexing time). These
tests were done on my 512 MB, Athon 64 2800 (very average machine) running
Ubuntu Linux. CDT
3.1.1
Initial index – 12.3 minutes
Reindex – 10.3 minutes HEAD
Initial Index – 122.2 minutes
Reindex – 119.6 minutes My
heart bleeds…. There
are still a few exceptions that I'm working on cleaning up, but I don't think
they'll impact these times much. I
will continue to monitor these times and give you regular reports. Doug
Schaefer, QNX Software
Systems Eclipse CDT Project Lead, Tools PMC Member
|