|
Hi, disk-usage calculates build disk usage by two ways - after build (to have info about build size as soon as possible) and in recalculation thread (which is executed by global configuration setting - as user wants it to be executed). So if you change build size after its build (delete something), disk-usage does not reflect this change until recalculation thread is executed. It is logical, in opposite approach disk-usage has to scan all builds for changes and recalculates them all the time - this would be a really performance issue, because calculation of disk usage is very expensive in large instances. Even current behaviour can cause performance issues in large instances.
|
