The new setup is definitely a good improvement. Is similar to my current HP laptop which has slightly older components, i9-13950HX and Nvidia RTX 3500.

It works ok for me, including multi station SX10 cloud processing, and working with high triangle count surfaces. My main Lidar/Scanned ground surface is filtered down from 4.5 million to 1 million triangles, and I tend to clip it with "Offset surface" to the area I'm working on. I currently work a lot with sideslopes for crane pads, access ramps and stockpile feasibility studies.

When you say "I am using earthworks" I assume you mean corridor modelling, sideslopes, volume calculations, surface handling?

The problem with those is that they are programmed single threaded only. There had been discussions here in the forum, and arguments from former Trimble employees, that this can't be multithreaded. But at least the corridor volume computation is one major candidate for multithreading, just give every CPU thread one part of the corridor and sum it up. The rest would require some major investment of resources, R&D and rewriting of code. And that's something that Trimble is never going to do. They don't even want to spend money to fix all the bugs that we report.

So, for the time being, the higher the single thread performance of the CPU the happier you gonna be. And the amount of RAM is also a good candidate for improvement, the 16 GB in your old machine are definitely a, if not the bottleneck. If I load my big project, a bloated 450 MB VCE file, I see a memory usage of 26.5/63.2 GB.

Ronny,

You are correct, I use earthworks for corridor modelling, sideslopes, volume calculations, surface handling. Thank you for all of the very useful information. I will probbaly jump on this laptop. From my research the i9-14600 HX has one of the best single core. 

The new setup is definitely a good improvement. Is similar to my current HP laptop which has slightly older components, i9-13950HX and Nvidia RTX 3500.

It works ok for me, including multi station SX10 cloud processing, and working with high triangle count surfaces. My main Lidar/Scanned ground surface is filtered down from 4.5 million to 1 million triangles, and I tend to clip it with "Offset surface" to the area I'm working on. I currently work a lot with sideslopes for crane pads, access ramps and stockpile feasibility studies.

When you say "I am using earthworks" I assume you mean corridor modelling, sideslopes, volume calculations, surface handling?

The problem with those is that they are programmed single threaded only. There had been discussions here in the forum, and arguments from former Trimble employees, that this can't be multithreaded. But at least the corridor volume computation is one major candidate for multithreading, just give every CPU thread one part of the corridor and sum it up. The rest would require some major investment of resources, R&D and rewriting of code. And that's something that Trimble is never going to do. They don't even want to spend money to fix all the bugs that we report.

So, for the time being, the higher the single thread performance of the CPU the happier you gonna be. And the amount of RAM is also a good candidate for improvement, the 16 GB in your old machine are definitely a, if not the bottleneck. If I load my big project, a bloated 450 MB VCE file, I see a memory usage of 26.5/63.2 GB.