GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
PS C:\> Measure-Command { Get-Process | Select-Object Name, Id | Sort-Object -Property Id }
Days : 0
Hours : 0
Minutes : 0
Seconds : 0
Milliseconds : 16
Ticks : 166182
TotalDays : 1.92340277777778E-07
TotalHours : 4.61616666666667E-06
TotalMinutes : 0.00027697
TotalSeconds : 0.0166182
TotalMilliseconds : 16.6182
Seconds : 1
Milliseconds : 37
Ticks : 10370187
TotalDays : 1.200253125E-05
TotalHours : 0.00028806075
TotalMinutes : 0.017283645
TotalSeconds : 1.0370187
TotalMilliseconds : 1037.0187
----
The performance difference seems minor in the above examples. However, when working with commands that gather data from multiple machines, or over the network, the difference in efficiency could be a significant factor in time to complete.