DelphiSpeedUp 2.8 Release Candidate

By | December 1, 2009

After all the responses to my last blog entry I started all over again and implemented a completely different optimization strategy. And thanks to some time consuming researches I think I found the best solution for the problem.

BTW: Delphi 7’s debugger has a problem if DEP (Data Execution Prevention) is active. It took me 4 hours to figure out that it weren’t my DelphiSpeedUp 2.8 changes that caused an access violation in the application process when I pressed F7 at a line that would jump into a function with debug information.

I’ve removed the compiler memory manager replacement code due to the reports about the “Out of memory” bug. This automatically solves the EInvalidPointer exception.

The Step-Into optimization is not available for Delphi 5. This means for Delphi 5 that DelphiSpeedUp 2.8 contains the same code that DelphiSpeedUp 2.78 contains.


Changes from version 2.78 to 2.8:

  • Added: Improves “Step Into” speed, especially for large projects or projects with packages (Supported for Delphi 6-2007).


Downloads:

DelphiSpeedUpV28.zip (Delphi/C++Builder 5 – 2007)

DelphiSpeedUpV28D6.7z (Delphi/C++Builder 6)

DelphiSpeedUpV28D7.7z (Delphi 7)

DelphiSpeedUpV28D2005.7z (Delphi 2005)

DelphiSpeedUpV28D2006.7z (Delphi 2006)

DelphiSpeedUpV28D2007.7z (Delphi/C++Builder 2007)

Maybe you must clear your cache first. You can see the difference in the Versions.txt file. The 2.8 beta release had a 2.78 Version.txt file.

4 thoughts on “DelphiSpeedUp 2.8 Release Candidate

  1. Roland

    Hallo Andreas

    Habe nun das neue DelphiSpeedUp mit D2007 auf Vista 64 getestet. Leider hat die Optimierung wie bei der alten Version keine Geschwindigkeitszuwächse beim Step Into gebracht. Wir haben aber bei unserem Projekt aufgrund der Größe auch bei D2009/D2010 die gleichen Probleme. F7/F8 funkt nur mit einer Verzögerung von 3-4 Sec.

  2. Andreas Hausladen Post author

    @Roland: 3-4 Sekunden ist für den Step-Into Bug eine sehr gute Zeit. Denn ohne meinen Patch braucht er, je nach Projektgröße, bis zu 3 Minuten. Deswegen schließe ich darauf, dass es bei dir eher die “Lokale Variablen” bzw. der Aufrufstack sind, welche die Zeit verschlingen. Einfach mal die beide Ansichen schließen/ausblenden. Dann sollte auch F7/F8 wieder schneller sein.

  3. Donald Shimoda

    Andreas,
    Thanks for your work. Work excellent here, in my D2007 pro.
    Please let me know if you need to run any additional test.

    Best regards.

  4. Ian Yates

    I’m still using D7 for most of our projects. F7 debugging has always been a pain. I’ll certainly give it a go and let you know if I have any issues. Much appreciated! 🙂

Comments are closed.