Please see the below explanation.
How does Capacity Command Center will make use of multiple cores?
Where are threads not used?
The only part of Capacity Command Center or Virtual Placement Manager that doesn't specifically use threads is the placement algorithm itself, which is optimized in most cases to be less than 10 seconds.
Note: Data is loaded from the database before the actual placement algorithm runs, that data load appears as part of the placement time but wouldn't be helped by threading the algorithm.