- Screenshot 2026-05-02 002858.png (26.79 KiB) Viewed 5142 times
Benchmarking CPU's in Command Modern Operations
Moderator: MOD_Command
-
Knightpawn
- Posts: 769
- Joined: Mon Dec 02, 2024 12:28 pm
Re: Benchmarking CPU's in Command Modern Operations
A bit faster. But I want to recover the below 1000 ms
Re: Benchmarking CPU's in Command Modern Operations
Once more, a bit faster here.
-
Knightpawn
- Posts: 769
- Joined: Mon Dec 02, 2024 12:28 pm
Re: Benchmarking CPU's in Command Modern Operations
Unfortunately the last build is very slow here. And this is the faster of 2, the second was 3224 ms.
I have also noticed a high CPU use, that does not translate into a faster simulation, at least in the benchmark scenario.
Confirmation?
I have also noticed a high CPU use, that does not translate into a faster simulation, at least in the benchmark scenario.
Confirmation?
-
Knightpawn
- Posts: 769
- Joined: Mon Dec 02, 2024 12:28 pm
Re: Benchmarking CPU's in Command Modern Operations
the horror!Nikel wrote: Fri Jun 26, 2026 5:01 pm Unfortunately the last build is very slow here. And this is the faster of 2, the second was 3224 ms.
-
Knightpawn
- Posts: 769
- Joined: Mon Dec 02, 2024 12:28 pm
Re: Benchmarking CPU's in Command Modern Operations
Very slow indeed compared to previous built
Re: Benchmarking CPU's in Command Modern Operations
Run the benchmark with B1877 and B1892 to compare the CPU use in the resource monitor and this is the result.
As you see the CPU use has increased significantly, is visible in the graphic and in the average CPU %. In the graphic the periods of 100% use are much more common, also the drops to 0%. The average changes along the benchmark, but it is noticeable the difference between the 2 builds, in B1892 was up to 80%.
However the result of the benchmark is worse, why?
Exceptions, none in B1877 running the benchmark. Several in B1892, as commented in the Top Gun scenario thread.
As you see the CPU use has increased significantly, is visible in the graphic and in the average CPU %. In the graphic the periods of 100% use are much more common, also the drops to 0%. The average changes along the benchmark, but it is noticeable the difference between the 2 builds, in B1892 was up to 80%.
However the result of the benchmark is worse, why?
Exceptions, none in B1877 running the benchmark. Several in B1892, as commented in the Top Gun scenario thread.
27-06-2026 16:40:02 -- Bv1.10 Beta - Build 1892 -- Collection was modified; enumeration operation may not execute. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified; enumeration operation may not execute.
Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Enumerator.MoveNext()
at lO5kXM1sbE6ISsOGxXRB.Cvw11DVDImG(Object , lO5kXM1sbE6ISsOGxXRB )
at Command_Core.ActiveUnit_AI.get_ConsidersToBeUnderAttack(Boolean IgnoreThreatIfNoSensor)
Call Stack & Error details:
Error at 100774:
27-06-2026 16:40:03 -- Bv1.10 Beta - Build 1892 -- Collection was modified; enumeration operation may not execute. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified; enumeration operation may not execute.
Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Enumerator.MoveNext()
at lO5kXM1sbE6ISsOGxXRB.Cvw11DVDImG(Object , lO5kXM1sbE6ISsOGxXRB )
at Command_Core.ActiveUnit_AI.get_ConsidersToBeUnderAttack(Boolean IgnoreThreatIfNoSensor)
Call Stack & Error details:
Error at 100774:
27-06-2026 16:40:03 -- Bv1.10 Beta - Build 1892 -- Collection was modified; enumeration operation may not execute. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified; enumeration operation may not execute.
Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Enumerator.MoveNext()
at lO5kXM1sbE6ISsOGxXRB.Cvw11DVDImG(Object , lO5kXM1sbE6ISsOGxXRB )
at Command_Core.ActiveUnit_AI.get_ConsidersToBeUnderAttack(Boolean IgnoreThreatIfNoSensor)
Call Stack & Error details:
Error at 100774:
27-06-2026 16:40:04 -- Bv1.10 Beta - Build 1892 -- Collection was modified; enumeration operation may not execute. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified; enumeration operation may not execute.
Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Enumerator.MoveNext()
at lO5kXM1sbE6ISsOGxXRB.Cvw11DVDImG(Object , lO5kXM1sbE6ISsOGxXRB )
at Command_Core.ActiveUnit_AI.get_ConsidersToBeUnderAttack(Boolean IgnoreThreatIfNoSensor)
Call Stack & Error details:
Error at 100774:
27-06-2026 16:40:04 -- Bv1.10 Beta - Build 1892 -- Collection was modified; enumeration operation may not execute. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified; enumeration operation may not execute.
Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Enumerator.MoveNext()
at lO5kXM1sbE6ISsOGxXRB.Cvw11DVDImG(Object , lO5kXM1sbE6ISsOGxXRB )
at Command_Core.ActiveUnit_AI.get_ConsidersToBeUnderAttack(Boolean IgnoreThreatIfNoSensor)
Call Stack & Error details:
Error at 100774:
27-06-2026 16:41:59 -- Bv1.10 Beta - Build 1892 -- Destination array was not long enough. Check destIndex and length, and the array's lower bounds. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Destination array was not long enough. Check destIndex and length, and the array's lower bounds.
Stack Trace: at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length)
at PrsEHVQ2XMeV5OovtjBy.Cvw11DVDImG(Array , Int32 , Array , Int32 , Int32 , PrsEHVQ2XMeV5OovtjBy )
at Collections.Pooled.PooledList`1.System.Collections.Generic.ICollection<T>.CopyTo(T[] array, Int32 arrayIndex)
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Command_Core.ActiveUnit_DockingOps.PickNewAssignedHost_RandomWithinRange(ActiveUnit excludeUnit)
Call Stack & Error details:
Error at 100155:
27-06-2026 16:42:06 -- Bv1.10 Beta - Build 1892 -- Collection was modified during enumeration. -- Scen : -- DB : b383294e8525920ba56f90cc4c61d6a3d86781e0 -- Exception: Collection was modified during enumeration.
Stack Trace: at Collections.Pooled.ThrowHelper.ThrowInvalidOperationException_InvalidOperation_EnumFailedVersion()
at Collections.Pooled.PooledList`1.Enumerator.EelWk5enful()
at Collections.Pooled.PooledList`1.Enumerator.MoveNext()
at Command_Core.Side.DropContact(Contact theC, Scenario& theScen, Boolean LogMessage)
at Command_Core.Side.HandleUnitGoingInoperative(ActiveUnit theUnit)
Call Stack & Error details:
Error at 101063:
Re: Benchmarking CPU's in Command Modern Operations
For the standard version running on a 9800X3D:
Last edited by SerLar on Mon Jun 29, 2026 12:35 am, edited 2 times in total.
Re: Benchmarking CPU's in Command Modern Operations
May you test the last B1892?
But backup first your current Command.exe.
Re: Benchmarking CPU's in Command Modern Operations
RAM: DDR5-4800. need to increase that
-
Knightpawn
- Posts: 769
- Joined: Mon Dec 02, 2024 12:28 pm
Re: Benchmarking CPU's in Command Modern Operations
Back to a more normal result after the bug in B1892 
Re: Benchmarking CPU's in Command Modern Operations
12900K, no idea if the result is good or not. Also added to Gdocs but unsure if I should have sorted it somehow, my line is now last.
Re: Benchmarking CPU's in Command Modern Operations
In the Command.ini file (Config folder).
This line is True or False?
This line is True or False?
RunCoreMultithreaded = True
Re: Benchmarking CPU's in Command Modern Operations
Back to back comparison during a CPU upgrade from Dual Socket Xeon 2640V4 to dual socket Xeon 2697A V4 both with 96GB RAM.
- Attachments
-
- Dual Xeon 2697AV4
- Screenshot 2026-10-21 183541.png (157.45 KiB) Viewed 695 times
-
- Dual Xeon 2640V4
- Screenshot 2026-10-20 221351.png (140.1 KiB) Viewed 695 times
Re: Benchmarking CPU's in Command Modern Operations
FalseNikel wrote: Tue Oct 20, 2026 1:25 pm In the Command.ini file (Config folder).
This line is True or False?
RunCoreMultithreaded = True
I havent modified that myself.
Re: Benchmarking CPU's in Command Modern Operations
May you retry the benchmark? Changing it to True and saving Command.ini
In my case the benchmark changes from 1675 to 1554.