From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9DAA1158089 for ; Sun, 17 Sep 2023 17:46:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4A63E2BC132; Sun, 17 Sep 2023 17:46:10 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 07A3F2BC016 for ; Sun, 17 Sep 2023 17:46:09 +0000 (UTC) Received: from host86-155-223-197.range86-155.btcentralplus.com ([86.155.223.197] helo=[192.168.1.99]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1qhvqP-000CkJ-8z for gentoo-user@lists.gentoo.org; Sun, 17 Sep 2023 18:46:08 +0100 Message-ID: <1acbc1b0-9f39-1fd6-3cc1-6d55ae5eef0d@youngman.org.uk> Date: Sun, 17 Sep 2023 18:46:05 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Content-Language: en-GB To: gentoo-user@lists.gentoo.org From: Wols Lists Subject: [gentoo-user] What is the point of baloo? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 95c96fe4-18fd-4fcf-9fde-955e371c1680 X-Archives-Hash: 16920d01cb1f02f151609582377ac952 It always annoys me, but baloo seems to be being an absolute nightmare at the moment. Iirc, it's "the file indexer for KDE" - in other words it knackers your response time reading all the files, wastes disk space building an index, and all for what? So that programs you never use can a bit faster? What the hell is the point of shaving 10% of a run time of no seconds at all? I tried to kill it and it appears to have just restarted. Is there a use flag I can use to just get rid of it completely? What I find really frustrating is it claims to have been "built for speed". If it's streaming the contents of disk into ram so it can index it, it's going to completely knacker your system response whatever (especially if a program I WANT running is trying to do the same thing!) Cheers, Wol