Most recent Manjaro installed and it is SOOOO SLOOOOWWWW after installation
ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You misunderstood me - I wasn't suggesting you install an indexer, but that the default indexer was likely the problem. Maybe ask on the Manjaro forum how to disable it.
I completely understood what you were saying! All I meant was there was no opportunity an indexer would be installed by me!! Installing even the tiny iotop took more than half an hour!!!
Still, if there exists an indexer installed, it won't be too hard to un-install it. Still, I don't really think there is one...
I completely understood what you were saying! All I meant was there was no opportunity an indexer would be installed by me!! Installing even the tiny iotop took more than half an hour!!!
Still, if there exists an indexer installed, it won't be too hard to un-install it. Still, I don't really think there is one...
Perhaps there is none, but SOMETHING is leveraging kwoerker to do a TON of I/O behind the scenes, and that is exactly what a KDE indexer acts like. He was not suggesting a firm diagnosis, but something that fits the symptoms to consider.
I avoided Gnome and KDE for the longest time because they were "heavy" and I prefer lighter options. Recent KDE seems faster, lighter, and feature rich. I have learned to like it very much. That said, if it ALWAYS indexed like that I would find another desktop option. This may be some option or default that the maintainers chose that is horribly inappropriate for your platform. It costs little to ask where they discuss, as they would know better than anyone.
Yes, but this is XFCE. I don't know how Manjaro configures XFCE, but what indexer can be at work there? Tumbler? I doubt it could thwart the system performance like this.
I haven't seen anything this bad, but had similar if less exaggerated that evaded diagnosis for over a year. Even persisted after I swapped out the disk. Eventually only found it by setting kernel traces on the i/O queues themselves. Tracker in my case.
But, if indexer of some kind is doing this, shouldn't it be spotted in top?! Wouldn't it be traced in the journal?! I'll check the packages installed for anything fishy.
But, if indexer of some kind is doing this, shouldn't it be spotted in top?! Wouldn't it be traced in the journal?! I'll check the packages installed for anything fishy.
Perhaps, or perhaps not.
I have found things by examining top and other process reporting.
Some things hide, either by design or by accident. If they trigger bursts of requests through a service the requester is idle most of the time, but the service SERVICING those requests goes CRAZY! You then can identify the servicing process using top, but you have not identified the PROBLEM.
As we migrate to more systemd focused services we see more and more of this, though I am not convinced that the nature of systemd is the cause. The ways we code and the things we take for granted on modern system may be the more significant factor.
In any case, the question here is "what is triggering the behavior?" and more to the point "how do we FIX this?"!
I might consider iotop for additional investigation.
I juist found a thread that might help. I suggest you look through the issue and comments at https://stackoverflow.com/questions/...-of-my-disk-io for some interesting reading. Some of this may apply directly to your investigation.
You may try and see if it helps. I doubt Tumbler is the culprit by itself though. It's just a thumbnail service. But one of Tumbler plugins is a possibility. Like e.g. cover thumbnailer that queries online services. You can just disable suspicious plugins in /etc/xdg/tumbler/tumbler.rc
As a workaround, ArchWiki suggests running this script at system startup.
I'll certainly do that, though I really doubt it's a bad block:
This is indeed the third time I re-partition the hard drive, and the behaviour is the same.
I can access Manjaro's partition from the other distro with no difficulties.
I could, of course, try an older version (since the one I'm struggling with is the latest...), but then it would, as expected, try to upgrade itself...
Oh, yes, I'm using other distroes!!! I have other machines with other Linux distroes. I've been since the mid-90's. It's just that I wanted to try Manjaro...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.