Everything folder size calculation is slow

Thanks, I've checked and it only shows the 3 drivers you listed.

In Everything 1.5a, there are columns for this: "child-count" for direct children and "descendant-count" for all children. Maybe you could try this query to see if you get the necessary results:

folder:parent:"C:\Example\" addcol:child-count: addcol:descendant-count:

image

1 Like

We can't use Everything 1.5 until it's out of alpha and has a published API.

As you know, 1.5a also works just fine with Dopus. Maybe it would be possible to add an advanced setting to enable this different type of query for users of that version. If the query works as expected (please try), it would solve the performance problem for everyone who has performance issues with a large index.

Edit: Well, I think it doesn't support access to any of the 1.5a columns via the SDK. It would still be useful to have instant folder sizes using a single folder:parent:"C:\Example\" query as long as there's no "count" columns enabled.

1 Like

I guess I will have to find time to read this discussion. I never was able to get the size to work right in beta or in the current release. It is so slow and some times doesn't even sort correctly.

Edit: I don't know about you guys but my everything uses a gig of ram... I have so many files and drives on my network

Would also love to finally be able to get instant sizes/counts everywhere! Is this lack of SDK still the main blocker?

Agreed, just the folder sizes would already be great with the counts being slower...

By the way, it seems there is an SDK for 1.5
https://www.voidtools.com/forum2/viewtopic.php?t=15853

The Everything 1.5 SDK is version 3 of the Everything SDK.
Version 2 is for Everything 1.4.
version 1 is for Everything 1.3.

1.4 vs 1.5 won’t be why things are slow, as lots of people are already using 1.5 with Opus without problems.

The SDK should mean we can make Opus work with 1.5’s default mode, but configuring it to be compatible with 1.4 means it already works with Opus, and lots of people are using it that way already,

I don't remember whether the file/folder counts were added in 1.5, but if they were, then yes, it will be why things are slow, since in 1.4 you'd have to do the enumeration yourself, and in 1.5 it would be just a single request

or those people don't realize they can get instant sizes instead of ~0.X sec, or they need to report their issues here. For example, I've noticed it the first day I've tried (in Everything UI everything is instant, in DOpus it became faster, but not instant), but since it's still fast, especially outside of things like C:, I simply forgot to look for issue report/file one myself until recently.

@eugenesv,

Nice finding.
I have checked, and for me, it takes approximately 4 seconds for DirectoryOpus to get all folder sizes when I open C:\Windows folder. However, if I search folder:c:\windows in VoidTools Everything 1.4.1.1026, the size column is shown instantly.

those people don't realize they can get instant sizes instead of ~0.X sec

Oh no! Now I realize it, and my life will never be the same. What have you done

I used to experience slow foldersizes showing up in Dopus, but rebuilding the complete Everything database fixed that.

@BuckyB,
Thank you for the suggestion.
Unfortunately, it hasn't helped.

How much time does it take for you to get all folder sizes when you open the C:\Windows folder?

Directory Opus 13.13.7 (Beta) Build 9190 x64
OS 10.0 (B:26100 P:2 T:1) SP 0.0
Everything 1.5a Version 1.5.0.1391a (x64)

@Hardkorn,

Could you please do the same but inside the C:\Windows folder?



Thank you. Amazing. It works very fast for you.

@PolarGoose How big is your Everything database?
I think the old SDK has that kind of issues if EV indexing is 'abused'. With the SDK3 (which also supports EV 1.4) there are no such problems.
So IMO the important here is not the Everything version, but the SDK version. v3 can get the data Opus requires in a single call, instead of several as it does currently. And you have to add the extra times that occur if the user abuses indexing features in EV, because the SDK.
But v3 is relatively new, there isn't even an updated official es.exe tool that is using it already! We'll have to be patient...

How big is your Everything database?

57MB (1 380 509 objects)