Assistance with >~95% CPU usage when calling pread64 when using LUKS
Boris-Barboris
ismailsiege at gmail.com
Mon Mar 11 08:29:56 UTC 2019
On Monday, 11 March 2019 at 03:43:19 UTC, abraunegg wrote:
> Thanks - yes that function / check could be better I agree,
> however that is not called when the system is simply checking
> the status of any changed files & folders. That is only used
> when checking if a 'new file' should be uploaded.
>
> In the issues posted, it simply seems to be the checking of
> each and every file / folder when there is zero rate of change
> - the only thing here is the enumeration of DirEntry items.
Sorry, I skimmed through the issues quickly. Given the sparsity
of info in the logs, I would be caughtious in assuming the
program internal state.
I can recommend trying to compile an easy to use instruction for
"callgrind" trace generation (there is a good page on dlang wiki
about it), wich, given a debug build of a program, should give
you an insight about what's happening.
I don't think there's much use of statically analyzing a source
code, you should try to extract more runtime info from the issue
reporters.
More information about the Digitalmars-d
mailing list