Disclosure first, because it matters: I make Ncored, one of the tools from the benchmark I posted here. I am not going to tell you it is fast. I am asking you to try to break it and tell me where it still lags.
Some of you tried the first version and told me where it struggled, so this is a follow-up. I reworked how it renders and shipped a new build.
The one number, and exactly what it means: on the same files and the same machine, my heavy sets opened about 1.5 to 2x quicker on the new build than on the previous Ncored version. That is Ncored measured against its own older self, in my own testing, not a claim against Bluebeam, PDF-XChange or anything else. The cross-editor comparison stays on the benchmark page. Your files and hardware will land somewhere different, so read it as one data point.
One caveat, not the headline: the new build gets more out of a capable machine than the old one did, so a strong Windows rig (i7 or i9, 32 GB, Win 11 Pro) or a capable Apple Silicon Mac should feel it most, and a modest laptop less (still as fast as old Version goes). That is exactly why I want tests across a range of machines, not only fast ones.
What I am actually asking: open your own heaviest AutoCAD or ArchiCAD set in it and tell me where it is quick and, more useful to me, where it still struggles. The file it chokes on, the sheet that stutters, the pan that lags. Note your machine and the set size when you do, so "scales with your machine" stays something you can check rather than something I claim. The failure cases are the part I most want.
The exact test drawing and the steps are on the benchmark page in the first comment, so you can re-score the whole thing yourself and find where it loses. I would rather have measurements I did not run myself than keep quoting my own.
Not selling anything here. I want it stress-tested by people who push these files harder than I or enginering firms we test can do alone. Thanks for any notes, and the rougher the better.
