warrentyexpired/ModernUO
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(core): Fixes core tick count for VMs (#600)

Browse source 
Some architectures (specifically docker) have an issue with tick count and high precision timing.
This handles those weird cases so instead of outright freezing, you may get timer precision loss.
This commit is contained in:
Kamron Batman 2021-05-13 18:22:42 -07:00 • committed by GitHub
parent 6dcf3aafe8
commit edea1d4906
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

20
Projects/Server/Main.cs
View file

@ -125,12 +125,26 @@ namespace Server
[ThreadStatic]
private static DateTime _now;
[MethodImpl(MethodImplOptions.AggressiveInlining)]
private static long GetTicks() => 1000L * Stopwatch.GetTimestamp() / Stopwatch.Frequency;
// For Unix Stopwatch.Frequency is normalized to 1ns
// We don't anticipate needing this for Windows/OSX
private static long _maxTickCountBeforePrecisionLoss = long.MaxValue / 1000L;
private static long _ticksPerMillisecond = Stopwatch.Frequency / 1000L;
public static long TickCount
{
get => _tickCount == 0 ? GetTicks() : _tickCount;
get
{
if (_tickCount != 0)
{
return _tickCount;
}
var timestamp = Stopwatch.GetTimestamp();
return timestamp > _maxTickCountBeforePrecisionLoss
? timestamp / _ticksPerMillisecond
// No precision loss
: 1000L * timestamp / Stopwatch.Frequency;
}
set => _tickCount = value;
}