Forum > LCL

[UPDATE] TOpenDialog - 100% CPU - Fan Revs Up

<< < (4/9) > >>

MarkMLl:
Oh $deity... I'm reminded of some of the filesystem tuning hacks related to turning off atime updates etc.

There is of course an xkcd for this https://xkcd.com/2531/

I wonder: does this depend on the desktop environment? The CPU might not be going to the open dialog(ue) per se, but to desktop code which is monitoring file creation in the background (using fam) and is unhappy that something is trying to read the directory at the same time as it's being updated... does top show anything useful?

MarkMLl

dbannon:

--- Quote from: MarkMLl on October 25, 2021, 10:34:32 pm ---Oh $deity... I'm reminded of some of the filesystem tuning hacks related to turning off atime updates etc.

There is of course an xkcd for this https://xkcd.com/2531/


--- End quote ---

Indeed turning off atime can speed up a file system that is handing a lot of files. In a previous life, it was a pretty standard thing to do where where each user had their own file system if they used lots of small files. Image processing, life sciences etc. And people almost never miss the information atime provided.

The degree of benefit did vary with the file system in use but as this was remote access, desktop never came into our equations so I cannot comment on that.

And, yes, there is a relevant XKCD, but there is a relevant XKCD for ANY situation.

Davo

del:
The app is called "CustomOps". Right now I'm using ffmpeg to capture two webcams and save the streams into sequences of jpegs. If I navigate the open file dialog into either of the jpeg directories it will freeze. The first "top" is running a debug build from Lazarus. The second "top" is running the release build from the command line.

dbannon:
well, now that fiddling with FS has been mentioned, its quite safe and does not really take away anything you need, to remove atime.  There are other settings that may also help but I would be less enthusiastic if its not a specialist mount for just one purpose.  But, atime is easy and safe, Windows users for example don't have an atime available any way.

Edit, as root, /etc/fstab, your home dir will probably be like -

--- Code: Pascal  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---UUID=a748839c-84fb-40cc-9b5b-caa902ab00ad /home    ext4    defaults     0    2
Add 'noatime', ahead of 'defaults', no space between.  Remount, easiest way to do that is reboot if you can.

--- Code: Pascal  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---UUID=a748839c-84fb-40cc-9b5b-caa902ab00ad /home    ext4    noatime,defaults    0    2
It will make a difference, I just don't know how big a difference !

Davo

del:
Thanks Davo. I did a "cat" of the file and got the results shown in the attached image. It looks like noatime is already set, but it's AFTER defaults. Do I need to do anything?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version