RE: RE: [opensuse] slow desktop action and hangs after upgrade to 42.1
-----Ursprüngliche Nachricht----- Von: Xen Gesendet: Sa. 02.01.2016 12:33 An: suse , Betreff: RE: [opensuse] slow desktop action and hangs after upgrade to 421
stakanov@freenet.de schreef op 02-01-2016 1:49:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Just saying... if an indexing service can cause up to 8 second delays in system responsiveness, something is really really wrong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
No, I would say this is a typical case of tradeoff. The niceness of baloo was set to be not noticeable for strong machines. Once done indexing you also do not "feel it" on less strong machines. But as the userbase of Linux is very widespread with young and nearly prehistoric machines, what is O.K. for most may not be O.K. for all. So either you set the niceness of the process to a lower level manually or you just wait after the first run that the indexing has finished. I do not see any "problem" there. If ever there is a problem it is as it always was: the QA process runs on virtualized machines that do check for hardware consistency but I do not think that these machines do also reproduce the slowness of real hardware. So if an indexing service can cause 8 seconds delays after the very first install, maybe that is acceptable provided(!) that the niceness is correct once the indexing has been run once. YMMV --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov@freenet.de schreef op 02-01-2016 13:11:
So if an indexing service can cause 8 seconds delays after the very first install, maybe that is acceptable provided(!) that the niceness is correct once the indexing has been run once. YMMV
For me, that would NEVER EVER EVER EVER EVER EVER EVER EVER be acceptable. I do not know what land you live in but ordinary folk do not accept such things. Such a thing also never happens on 'any competing product'. Windows or Mac operating systems do not create 8 second delays. For instance, you can run Winamp indexing service on an entire harddisk with thousands of files it wants to know about and it will never cause any noticeable delays in anything. As such, I even doubt if Baloo is the culprit here. But if it is taking up 5GB of ram, then maybe something is wrong regardless. I did have 8-second delays on Windows recently. It was caused by corrupted user profiles. For the life of me I cannot imagine that Baloo would cause this. It requires pretty expert programming to create a program that can disrupt a system to this large an extent. I don't think they are good enough for that ;-). Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On January 2, 2016 4:11:24 AM PST, stakanov@freenet.de wrote:
-----Ursprüngliche Nachricht----- Von: Xen Gesendet: Sa. 02.01.2016 12:33 An: suse , Betreff: RE: [opensuse] slow desktop action and hangs after upgrade to 421
stakanov@freenet.de schreef op 02-01-2016 1:49:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Just saying... if an indexing service can cause up to 8 second delays in system responsiveness, something is really really wrong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
No, I would say this is a typical case of tradeoff. The niceness of baloo was set to be not noticeable for strong machines. Once done indexing you also do not "feel it" on less strong machines. But as the userbase of Linux is very widespread with young and nearly prehistoric machines, what is O.K. for most may not be O.K. for all. So either you set the niceness of the process to a lower level manually or you just wait after the first run that the indexing has finished. I do not see any "problem" there. If ever there is a problem it is as it always was: the QA process runs on virtualized machines that do check for hardware consistency but I do not think that these machines do also reproduce the slowness of real hardware. So if an indexing service can cause 8 seconds delays after the very first install, maybe that is acceptable provided(!) that the niceness is correct once the indexing has been run once. YMMV
Yes, in theory, but NO, not with the current version of Baloo. These problems were all solved about a year ago and Baloo is quite acceptable even on older machines like mine. There is no way it would cause 8 second delays. Its nice level is already sent to avoid that. Baloo just doesn't index that much stuff anyway. Specifically it does NOT index an entire drive in its default setup. Delays of that duration can happen when you have disk errors, unreadable track or sectors sitting right on top of frequently needed data. Especially if the disk drive has exhausted all of its reserved tracks. Somebody should look into SMART read outs on those drives. Blaming current versions of Baloo is up the wrong tree barking. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2016 08:11 PM, stakanov@freenet.de wrote:
No, I would say this is a typical case of tradeoff. The niceness of baloo was set to be not noticeable for strong machines. Once done indexing you also do not "feel it" on less strong machines. But as the userbase of Linux is very widespread with young and nearly prehistoric machines, what is O.K. for most may not be O.K. for all. So either you set the niceness of the process to a lower level manually or you just wait after the first run that the indexing has finished. I do not see any "problem" there. If ever there is a problem it is as it always was: the QA process runs on virtualized machines that do check for hardware consistency but I do not think that these machines do also reproduce the slowness of real hardware. So if an indexing service can cause 8 seconds delays after the very first install, maybe that is acceptable provided(!) that the niceness is correct once the indexing has been run once. YMMV
--- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen
I have been on my machine now for about an hour with the new KDE after letting it run all night. No noticeable delays, seems like once the baloo thing passed through everything went clear. Thanks to everyone for your help! -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 13.2 | KDE 4.14 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
George Olson -
John Andersen -
stakanov＠freenet.de -
Xen