Scheduler-test: investigate further breakage
...which turns out to be due to the DUMP-Statements, which seem to create quite some contention on their own. Test cases with very tight schedule will slip away then; without print statement everything is GREEN now
This commit is contained in:
parent
b0bde3f0b2
commit
23a3a274ce
2 changed files with 14 additions and 4 deletions
|
|
@ -84,7 +84,7 @@ namespace test {
|
|||
{
|
||||
simpleUsage();
|
||||
verify_StartStop();
|
||||
// verify_LoadFactor(); // broken, presumably by lates adjustments to control logic
|
||||
verify_LoadFactor();
|
||||
invokeWorkFunction();
|
||||
scheduleRenderJob();
|
||||
walkingDeadline();
|
||||
|
|
|
|||
|
|
@ -93337,13 +93337,23 @@ Date:   Thu Apr 20 18:53:17 2023 +0200<br/>
|
|||
</node>
|
||||
</node>
|
||||
</node>
|
||||
<node BACKGROUND_COLOR="#fdfdcf" COLOR="#ff0000" CREATED="1702233903855" ID="ID_135325176" MODIFIED="1702234289639" TEXT="derzeit gebrochen...">
|
||||
<node COLOR="#5b280f" CREATED="1702233903855" FOLDED="true" ID="ID_135325176" MODIFIED="1702349576130" TEXT="derzeit nichts mehr gebrochen...">
|
||||
<linktarget COLOR="#fd1e2b" DESTINATION="ID_135325176" ENDARROW="Default" ENDINCLINATION="-1191;124;" ID="Arrow_ID_1659622275" SOURCE="ID_1034326065" STARTARROW="Default" STARTINCLINATION="-482;-1288;"/>
|
||||
<icon BUILTIN="button_cancel"/>
|
||||
<node BACKGROUND_COLOR="#e0ceaa" COLOR="#690f14" CREATED="1702234284642" FOLDED="true" ID="ID_1005966089" MODIFIED="1702349566942" TEXT="verify_LoadFactor">
|
||||
<icon BUILTIN="broken-line"/>
|
||||
<node BACKGROUND_COLOR="#fafe99" COLOR="#fa002a" CREATED="1702234284642" ID="ID_1005966089" MODIFIED="1702234291764" TEXT="verify_LoadFactor">
|
||||
<icon BUILTIN="broken-line"/>
|
||||
<icon BUILTIN="stop-sign"/>
|
||||
<node CREATED="1702234306657" ID="ID_1728259651" MODIFIED="1702234310206" TEXT="nur ein Peak"/>
|
||||
<node CREATED="1702234311390" ID="ID_95265558" MODIFIED="1702234322625" TEXT="worker contention"/>
|
||||
<node CREATED="1702349219743" ID="ID_1468121979" MODIFIED="1702349405769" TEXT="Scheitert nur mit Scheduler-DUMP code">
|
||||
<icon BUILTIN="closed"/>
|
||||
<node CREATED="1702349271342" ID="ID_1109946237" MODIFIED="1702349287518" TEXT="zeigt ein sich massiv aufbauendes Backlog"/>
|
||||
<node CREATED="1702349288201" ID="ID_573592405" MODIFIED="1702349299578" TEXT="im Dump sieht man "contention""/>
|
||||
<node CREATED="1702349300304" ID="ID_668950871" MODIFIED="1702349325985" TEXT="zwischen zwei erfolgreichen Schedules vergehen ~200µs (statt ~10µs wie erwartet)"/>
|
||||
<node CREATED="1702349333171" ID="ID_1428514999" MODIFIED="1702349388653" TEXT="⟹ die "Contention-Probleme" werden wohl stark von den DUMP-Statements / COUT verursacht">
|
||||
<icon BUILTIN="idea"/>
|
||||
</node>
|
||||
</node>
|
||||
</node>
|
||||
<node COLOR="#435e98" CREATED="1702234301008" FOLDED="true" ID="ID_132335253" MODIFIED="1702347285923" TEXT="scheduleRenderJob">
|
||||
<icon BUILTIN="broken-line"/>
|
||||
|
|
|
|||
Loading…
Reference in a new issue