gi1242

Hi All,

I recently tried out the KDE/Plasma search (Baloo).

1. Indexing full content was too slow (I have some 100GB of data), and I disabled it.

2. Indexing filenames only was reasonably quick.

3. The search was very restrictive (full words only, miscategorized files). To make it usable for me, I had to get a list of all files and dump it to fzf, which worked reasonably well.

4. Using baloosearch6 to get a long list of files provides almost no noticable performance improvment over fd:

    > time ( baloosearch6 mimetype:application/pdf | wc -l )
    0.05s user 0.03s system 111% cpu 0.069 total
   
   
    > time ( \fd -H --no-ignore-vcs --xdev -tf -tl '.pdf$' | wc -l ) 
    0.24s user 0.15s system 364% cpu 0.107 total
   

   (Both commands found about 11,000 files. I'm using a SSD with about 500mbps read speed).

5. If I try it again with a larger file set :

    > time ( baloosearch6 -d VSync/ '' | wc -l ) 
    0.23s user 0.10s system 123% cpu 0.264 total
   
    > time ( \fd -H --no-ignore-vcs --xdev -tf -tl --base-directory=VSync/ | wc -l )
    0.13s user 0.11s system 456% cpu 0.052 total
   

   This time baloo found 96000 files, and fd found 59000 files. (fd might have run faster cause of disk caching.)

fd used more CPU no doubt. But the wall time difference in performance is so small that it doesn't make sense to me to use an indexed search anymore.

Any thoughts?

or be boring and alias sl=ls

Unpaid Basar journalists write story following up on the tragic death of a six-month-old girl who had got caught in a crossfire the previous year as well as landmine deaths in the region. They also report on conditions of new schools, the salaries of teachers and the implementation of government schemes in the area.

One of the authors is murdered and his body is found in a septic tank in the area near his home. He was 32 years old. The main suspect was Contractor Suresh Chandrakar, who had recently had an extravagant wedding for which he’d used a helicopter and organised Russian dancers, and was a distant relative of the victim.

his post on mastodon is here:

https://mastodon.social/@pixelfed/113849098386232034

Dear Mark, I hope this finds you well. I noticed something interesting today - it seems Instagram is blocking links to my little open-source project. You know, the one that lets people share photos without harvesting their personal data or forcing algorithmic feeds on them. I have to admit, I'm flattered. Who would've thought a small team of volunteers could build something that would catch your attention? We're just trying to give people a choice in how they share their memories online. No VCs, no surveillance capitalism, just code and community. Remember when Facebook started? It was about connecting people, not maximizing engagement metrics. Our project might be tiny compared to Instagram, but we're staying true to that original spirit of social media - giving people control over their online presence without turning them into products. You could've ignored us. Instead, by blocking our links, you've given us the best endorsement we could ask for. You've confirmed what we've been saying all along - that big tech is more interested in protecting their walled gardens than fostering genuine innovation. Every time you block a link to our platform, you remind people why we built it in the first place. Your action tells them there are alternatives worth exploring, ones that respect their privacy and agency. So thank you, Mark. You've turned our little project into a symbol of resistance against digital monopolies.