Leaderboard

New version (2.5) uploaded. Changes since last upload: Include/exclude modules/units from pdb. This helps keep the size of the pdb down and thus reduces the symbol resolve time in VTune. You no longer need to link your projects with debug info. map2pdb will reuse the existing debug section in the exe/dll/bpl if there is one. Otherwise it will create a new one. https://bitbucket.org/anders_melander/map2pdb/downloads/ What's next: Refactoring of the logging code. The current logging is basically just some functions that calls WriteLn. This should be replaced with a pluggable log framework so the whole logging mechanism can be replaced. The end goal is to enable integration of the map2pdb core into other projects. A jdbg reader. Embarcadero does not supply map files for the RTL/VCL rune time packages. Instead they ship jdbg files that can be read with the JEDI debug functions. The jdbg are built from map files so supposedly they contains much, if not all, of the information we need. The task here is to write a reader for the jdbg file format so we can produce pdb files from them. Figure out why VTune is so slow. A never ending task it seems.

I should clarify, ongoing defects considered and compared, Delphi has no more stability problems on my AMD vs Intel laptop. I acknowledge that if the hardware gives me perceived stability, it is likely masking race conditions. My Intel laptop is not likely be more than 10-15% slower in this workload, both are SSD as David points to. Laptops suffer from heat, as soon as the processor gets hot it starts to throttle down. The new desktop has plenty of cooling so it stays at full throttle. Your goal with an AMD build has to be keep it cool to maintain full core speed. So the speed gain is likely staying at full throttle, with a little extra clock speed. If you are looking at a 5600 you should be running more than just Delphi to actually use those 6 cores and the cache you are buying.

I don't see l any good reason why the IDE stability would have anything to do with hardware. It's just bug ridden. Those AMD processors are pretty tasty. Gamers love them. But they are way over powered for Delphi. Most important thing you can do for Delphi IDE perf is have a good SSD.

The available information can be found at: http://docwiki.embarcadero.com/RADStudio/Sydney/en/Code_Insight_Reference You can always try to enable logging and read the logfiles.

https://delphisorcery.blogspot.com/2021/03/how-to-hide-codeinsight-status-panel.html

I have been running 10.4.2 for 2 months on a AMD 5600X with no stability problems. Mine is a desktop build, so cooling is easy to keep under control. The IDE is very responsive, LSP definitely performs better compared to my laptop, Compile time is 20-30% improved. IDE stability is likely linked to the graphics card / driver underneath more than the processor. I did go very low end with an NVIDIA GT 1030 from a good supplier ASUS.

Yes, paths are meant to be encoded within the path delimiters, not / itself, unless after ? So I did the simple fix of only handling space. About 20 links failed my own tester with full encoding. So a new version is in SVN. That Canadian site also broke the ICS proxy due to not supporting absolute URLs used by proxies, that's been on my list to fix for a year, so got done as well. Testing is always useful, gets me to fix things. Angus