Project

General

Profile

Bug #10578

Native Scheduler reserves memory but does not use it completely

Added by Evgeny Novikov 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Scheduling
Target version:
Start date:
11/16/2020
Due date:
% Done:

0%

Estimated time:
Detected in build:
git
Platform:
Published in build:

Description

When Core generates complicated verification tasks that could not be solved quickly by task workers I observe the situation when Native Scheduler reserves most memory and thinks that it solves many verification tasks according to statistics shown in Bridge and in its own log, but this does not actually happen. There are just several active task workers that may occupy little memory thanks to speculative scheduling (according to a process table). This can result in rather inefficient usage of computational resources.

History

#1

Updated by Ilja Zakharov about 2 months ago

  • Status changed from New to Resolved

Fixed in fix-10578.

#2

Updated by Evgeny Novikov about 2 months ago

  • Status changed from Resolved to Closed

Tests passed, so, I merged the branch to master in ea26920c0. Let's hope that we will get verification results much faster!

Also available in: Atom PDF