Trimble Business Center

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

Hi Tyler,
yes the lack of multithreading has been discussed before.
https://community.trimble.com/communities/community-home/digestviewer/viewthread?MessageKey=40bc31a5-f513-46ed-9d21-0d3884f5fd08&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d&tab=digestviewer#bm40bc31a5-f513-46ed-9d21-0d3884f5fd08
But I'm with you, there are opportunities to improve it, i.e. the corridor earthworks report. Instead of having one core going through the whole corridor it should be easy to give each core one section of the corridor. Also the earthworks report. It should be possible to split share the volume prisms between all cores.

See this thread here, and especially comment 4 from Alan Sharp.
https://community.trimble.com/communities/community-home/digestviewer/viewthread?MessageKey=f8cf48f9-299c-4c3e-97f5-bc3ecc9c1bcc&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d&tab=digestviewer#bmf8cf48f9-299c-4c3e-97f5-bc3ecc9c1bcc

My guess is actually that it is not profitable enough to improve working functions. It would make it better for existing customers, but they are paying already. Only new customers bring extra money. And they are only attracted by new features on the list.

And that's not just for TBC. An even worse example is Worksmanager. It works just about so, still got heaps of flaws and actual bugs, and I haven't seen any improvement in the last 6-8 month. What a crash landing that one is compared to the Legacy TCC.

------------------------------
Ronny Schneider
------------------------------

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

It's a shame that for as powerful as the program can be, it feels so archaic now. It's incredibly clunky, which is made even more apparent when using high-performance setups.

With Trimble's new push toward subscription payments and seeming unwillingness to improve on already existing features, our organization has started to look toward other solutions for our data management and production. Existing customers might not bring in new money, but they do provide the economic base, and we're on the verge of dipping out if things don't start improving.

------------------------------
Tyler Lindsay
------------------------------

Original Message:
Sent: 02-11-2021 20:56
From: Ronny Schneider
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Hi Tyler,
yes the lack of multithreading has been discussed before.
https://community.trimble.com/communities/community-home/digestviewer/viewthread?MessageKey=40bc31a5-f513-46ed-9d21-0d3884f5fd08&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d&tab=digestviewer#bm40bc31a5-f513-46ed-9d21-0d3884f5fd08
But I'm with you, there are opportunities to improve it, i.e. the corridor earthworks report. Instead of having one core going through the whole corridor it should be easy to give each core one section of the corridor. Also the earthworks report. It should be possible to split share the volume prisms between all cores.

See this thread here, and especially comment 4 from Alan Sharp.
https://community.trimble.com/communities/community-home/digestviewer/viewthread?MessageKey=f8cf48f9-299c-4c3e-97f5-bc3ecc9c1bcc&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d&tab=digestviewer#bmf8cf48f9-299c-4c3e-97f5-bc3ecc9c1bcc

My guess is actually that it is not profitable enough to improve working functions. It would make it better for existing customers, but they are paying already. Only new customers bring extra money. And they are only attracted by new features on the list.

And that's not just for TBC. An even worse example is Worksmanager. It works just about so, still got heaps of flaws and actual bugs, and I haven't seen any improvement in the last 6-8 month. What a crash landing that one is compared to the Legacy TCC.

------------------------------
Ronny Schneider

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

The takeoff report is one of those commands that is famously slow and seems like it could be multithreaded.  I commonly have takeoff reports that take hours to complete on very high computers.  With processors starting to come out with over 1000 cores it really feels like multithreading is necessary.  I understand that it may not always be possible, but it used to not be possible to fly until someone figured it out, lets get someone smarter than the rest of us on staff and get it figured out.

------------------------------
Wayne Welshans
------------------------------

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

I to think that Trimble has pretty much dropped the ball on this.  I brought this up 3 or 4 years ago when I got an AMD chip set and it made now difference on my speed.  Very disappointed and Trimble really didn't care much at all.  At that time there was quite a few other people spending over 10k on setups and what we found is that TBC is a single thread old system that they basically have tried to polish up and make it look new.  Just look at the symbol library, it is Terramodel's old library.  You can't even move text that has a leader line and have it update the leader in real time as you move the text.  I could go on and on.  There are things that TBC does well but they really need to put some real time in coming up with a better program if they are going to cram this down our throats and make everyone use one program for the most part.  I don't even talk to people who run civil 3d because they laugh at the problems I have.  Its embarrassing.  And I am glad that Worksmanger was brought up, that to has been a crash landing as you say.  They want you to convert everything to it but when there system goes down you pretty much hosed because they dang sure don't want you transferring files with a thumb drive.  That would create a nightmare to line out on TCC.  While I am at it, why doesn't siteworks let you make notes?  Your surveying and you need to make notes about weather and station set ups that certain jobs require you to do.  Maybe Trimble thinks they are so big that they have created a bubble and they are comfortable working inside there bubble and don't care what happens outside of it.

So if anyone knows of a really fast single or dual core chip let me know lol!

Ben

------------------------------
Ben Ryschon
------------------------------

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

4 years later and it's still very slow with large projects.  Love TBC, but come on already.     

------------------------------
Jason Sommers
------------------------------

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

This won't ever happen. We can't even get the most basic of core features and tools remotely close to optimized. I usually just open multiple instances of TBC and work on different projects at the same time. At least they didn't claim they were going to do this, only to never deliver like they've done with so many other things.

------------------------------
steve schuler
------------------------------

Original Message:
Sent: 05-18-2025 11:55
From: Jason Sommers
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

4 years later and it's still very slow with large projects.  Love TBC, but come on already.     

------------------------------
Jason Sommers

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

Its simple for me. Just sit down at C3D and TBC with the same DXF or DWG file. Pan around and zoom in and out. Ask yourself why you are paying for TBC.

C3D doesn't even use multicore for much of its operations and its wildly better.

I wouldn't even buy TBC if it wasnt for the point cloud software which is phenomenal.

------------------------------
Jordan Koehn
------------------------------

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

TBC seems to be getting increasingly slow and clunky.  I've build in regular coffee breaks into my workflows to account for the time I can spend waiting for operations to complete!

------------------------------
Stevie McCafferty
------------------------------

Original Message:
Sent: 05-19-2025 07:12
From: Jordan Koehn
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Its simple for me. Just sit down at C3D and TBC with the same DXF or DWG file. Pan around and zoom in and out. Ask yourself why you are paying for TBC.

C3D doesn't even use multicore for much of its operations and its wildly better.

I wouldn't even buy TBC if it wasnt for the point cloud software which is phenomenal.

------------------------------
Jordan Koehn

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

I agree with you all. I have had a look and other programs of this nature don't use multi threading either. THanks

------------------------------
David Treasure
------------------------------

Original Message:
Sent: 05-20-2025 07:04
From: Stevie McCafferty
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

TBC seems to be getting increasingly slow and clunky.  I've build in regular coffee breaks into my workflows to account for the time I can spend waiting for operations to complete!

------------------------------
Stevie McCafferty

Original Message:
Sent: 05-19-2025 07:12
From: Jordan Koehn
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Its simple for me. Just sit down at C3D and TBC with the same DXF or DWG file. Pan around and zoom in and out. Ask yourself why you are paying for TBC.

C3D doesn't even use multicore for much of its operations and its wildly better.

I wouldn't even buy TBC if it wasnt for the point cloud software which is phenomenal.

------------------------------
Jordan Koehn

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

Unfortunately the Point cloud tools are also giving me issues with the new 2024.12, and don't even work consistently....

------------------------------
Aaron Carter
------------------------------

Original Message:
Sent: 05-19-2025 07:12
From: Jordan Koehn
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Its simple for me. Just sit down at C3D and TBC with the same DXF or DWG file. Pan around and zoom in and out. Ask yourself why you are paying for TBC.

C3D doesn't even use multicore for much of its operations and its wildly better.

I wouldn't even buy TBC if it wasnt for the point cloud software which is phenomenal.

------------------------------
Jordan Koehn

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------

Glad to see i am not the only one. TBC has so many great features but it is time for a revamp. We have tried all sorts of computer setups, processors, graphics card combinations and to no avail.  A high performance system gains you essentially nothing. Very frustrating.  This software is the same base code that we have been using for almost 15 years maybe longer. If you are listening Trimble its time to step it up. Point cloud processing works fantastic but as far as viewing and working within the cloud, forget it.   Why is it that turning off point clouds in the view filter manager is instant but turning them off in the registration command takes forever?  There is just no consistency and some features are very glitchy.     I could understand if this was buy it once software but we are paying HUGE maintenance fees to stay up dated but all we are really getting is paying for their bug fixes??   some of these new features are "cool" but i would prefer my money goes towards bringing the software into 2025 instead of adding more glitchy features.   

------------------------------
sean maxwell
------------------------------

Original Message:
Sent: 05-21-2025 10:34
From: Aaron Carter
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Unfortunately the Point cloud tools are also giving me issues with the new 2024.12, and don't even work consistently....

------------------------------
Aaron Carter

Original Message:
Sent: 05-19-2025 07:12
From: Jordan Koehn
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

Its simple for me. Just sit down at C3D and TBC with the same DXF or DWG file. Pan around and zoom in and out. Ask yourself why you are paying for TBC.

C3D doesn't even use multicore for much of its operations and its wildly better.

I wouldn't even buy TBC if it wasnt for the point cloud software which is phenomenal.

------------------------------
Jordan Koehn

Original Message:
Sent: 02-11-2021 16:40
From: Tyler Lindsay
Subject: Enhancement Request: Optimize TBC to use multiple CPU cores

I read somewhere that TBC only uses 1 CPU core most of the time, and that only point cloud processing would ever really be a viable task for using multiple cores.

I would think that generating large takeoff reports (i.e. multiple surfaces generated, multiple AOI's considered, multiple site improvement regions, etc.), updating multiple surfaces simultaneously, or even creating cut-fill maps could be optimized by using multiple CPU cores (cut-fill maps are generated by comparing delta elevations between surfaces at every point, so it seems like those surfaces could be divided into regions similar to point cloud processing).

At any rate, each of these tasks could certainly be optimized. These processes in TBC can take an extremely long time, whereas in many cases the same tasks can be completed in Civil3D nearly instantaneously.

------------------------------
Tyler Lindsay
------------------------------