I have a question regarding cpu usage on ZimaOS.
I have performed yesterday a large transfer that took a few hours to complete and since it has finished i still notice the ‘searchd’ process utilising my CPU 100% and keeping the cpu% at 35-45% at 50-60C while before the transfer it was idling at 18-20% with lower cpu temps 35-40C.
Is this indexing? How long does it usually run for? Since there is no way to monitor the indexing process and completion %.
Will it stop when the disk is checked? So far it has been running like this for several hours.
thank you for the reply. At least i now understand what it is doing.
is it also possible to implement that the system shows a % completion or time left for indexing/rebuilding RAID/expanding RAID processes?
it would be very helpfull to be able to view some more info on what the system is doing in the background.
Glad to hear that as mine has been running at high temps for over 3 days constantly. Not to mention the numerous times I have had to shut it down using “systemctl stop zimaos-search”.
Bad part about that is that you get an error of “Search service is not ready, please try again later.” if you try to search using the included files app on your Zimacube.
So high temps over long periods of time or no search function.
I want to start off my saying that I’m still learning and not a extremely experienced Developer or anything like that, so please excuse if there is an answer to my question that should be apparent.
My question that is not specifically about ‘searchd’ process utilizing 100% CPU but about the /dev/root partitioning of the drive. When I look at the file structure after installing ZimaOS 1.3.2-beta2, /dev/root is 1.3G in size and 1.3G is being used. From my understanding utilizing 100% of the root could be problematic and not having additional space can could cause performance and stability issues. Is that correct? I noticed that /dev/root shows the same thing in the image that @t1ll1s posted.
I installed ZimaOS on my 1TB Samsung Evo Plus SSD attached to a PCIe NVMe to NGFF SSD adapter on my ZimaBoard 432.
I did try to run GParted and removed 100GB from my /dev/nvme0n1p8 which originally had 904G in storage available with the intention making the root filesystem / larger. After taking down the /data partition down to 800GB it would not allow me to increase the root file system (/) (/dev/nvme0n1p3) but because it was not recognized due to an unknown file system which I later found out was SquashFS and that is read-only.
Please let me know if I’m right in my thinking that the Root File system needs additional storage and how I can ensure that 100% of my root partition is not being used. Any advice, feedback or education is much appreciated.
Hopefully in future updates, we can disable the ‘AI Search’ feature. Actually, I don’t need it myself, because I’m used to managing my files neatly and orderly.
