ID 578843 - Trackers take increasingly longer to create Baked Transform nodes as the number of keyframes increases

Problem summary:
Trackers take increasingly longer to create Baked Transform nodes as the number of keyframes increases
 
Customer reported version:
Nuke 15.0v4
 
Customer reported platform:
Rocky 9
 
Steps to reproduce:
1) Launch Nuke and open the attached tracker_example.nk file.
2) Run the code below (or similar) in the Script Editor to compare the time required to generate a Baked Transform node from each Tracker:

import datetime for number in [250,500,1000,2000,4000]:     tr = nuke.toNode("Tracker_%s"%number)     startTime = datetime.datetime.now()     tr["createCornerPin"].execute()     duration = datetime.datetime.now() - startTime     print("%s frames - %s seconds"%(number, duration.total_seconds()))

3) Observe that as the number of frames increases, it takes a seemingly exponentially longer time for the Transform node to be created: 

 
Expected behavior:
Trackers with more keyframes should not require an increasingly long time to create Baked Transform nodes.
 
Actual behavior:
When a Tracker node's number of keyframes increases, exporting a Transform (stabilize, baked) or Transform (match-move, baked) node will take longer and longer.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 15.0v4 - Windows 10, macOS 13 Ventura
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
 
Earliest version tested:
Nuke 12.0v1 - This issue appears to be in all tested versions of the product