Sort

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Sort

Post by nagan »

Using 653b x 86 . I made a sort for size and after it is done , immediately sorted for date modified (or any column). It does seem to add up some more incremental time ,say 5s whereas in 649b the second sorting (any column) was immediate. I checked that too as I write...
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

I will look into optimizing this.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

After sorting for size , if I attempted to sort by "Type" which I have enabled Everything crashes. I have made a few unicode files with unicode extensions. This happens both in x64 and x86.


It seems you have changed the working of "Sort". In this version I find it also a little slower added to the delay in the successive sorts which I have already mentioned.(x64 and x86)
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

Sorting by sizes, dates, types and attributes has been completely rewritten for 653.
Thanks for pointing out the type sort crash.

I am working on optimizing the sort, it should be the same speed as before.

I hope to release an update very soon.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

656b x 86
The sorting have come back to their original speed and successive sorts are immediate! Only the type column takes up a marginal increment of time.
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

I will look at optimizing type name sorting to match previous speeds.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

x64
1.I made a search dc:<2002 and in a haste pressed Enter , leading to the obfuscating of Everything Window had to close and restart. (Not repeatable again strangely , when I tried that later. No idea what could have caused it)

2. After restarting Everything I made a search again of dc:<2002 , it seemed taking very long. Cancelled the query and did a sort of "Date created". Once again it seemed to take ages and surprisingly the processor was showing Everything at 5% when usually it is above > 25% in my system. Finally it did sort but was slow.

3.I closed and restarted Everything. Behavior 2 is not repeatable. The sort is fast.

This is for info only and to report there are strange time(s) when Everything does not take up fast with the processor.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

x86
Today on restarting I pressed to sort by size.It was immensely slow combined with high disk usage and low processor use.This one strikes at random and am not able to replicate it , when after closing ET and restarting size sort is normal. Perhaps the user who had written about sorting with filters would also have got into this behavior...
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

Do you have any folder indexes that may be offline?
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

Do you have any folder indexes that may be offline?
Yes. The Pen drive which I often connect and disconnect.
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

Offline folders could be causing the slow caching of extended file information.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

x86
Started Windows ,I have just made ET(Everything) run. I clicked on size sort. Once again very negligible processor usage by ET , and also immense HDD flicker throughout ,like the Hard drive is scanned while building a database. I stopped it after say 50 sec , closed Everything , restarted and did the size sort , which is now normal and fast within 15 seconds. So I wonder what could have changed within 2 sessions of Everything.

Since I could observe the behavior in x64 too at random , the cause is there...
What could trigger a database build? or disk access when a sorting is attempted , because if it were an issue with offline drive , Hard disk would not have been scanned..

Next time perhaps I will attempt a debug mode in XP if it is still required.....
EDIT
THis time I got it in WIn 7 x64. After resuming , I closed the running instance of ET , started the debug mode and attempted the size sort , which nearly took 3 minutes.Later I clicked on some other column to ensure whether the successive sort was fast , and it was fine..
Slow sort.

Code: Select all

load localization
load everything icon
create mutex
bookmarks
set hook
create tray
db_load
new thread (0)
_db_filesystem_add 0: 0, 00000000003c5140
_db_filesystem_add 1: 0, 00000000003c51a0
_db_filesystem_add 2: 0, 00000000003c5200
_db_filesystem_add 3: 2, 00000000003e2970
SHChangeNotifyRegister: 1575416 36867 1 0
bind to family 23, protocol 6, socktype 1
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 692 0.000185
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 692 0.000146
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 692 0.000133
bind to family 2, protocol 6, socktype 1
ETP server online.
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000000000, curre
nt focus 0000000000000000
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 728 0.000869
find recent changes on C:
enter setfocus
leave setfocus
invalidate
enter main loop
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 728 0.001420
find recent changes on D:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 728 0.001113
find recent changes on F:
loaded 8363 of 267302 changes in 3.888042 seconds
recent changes memory usage: 464159 bytes
loaded 136 run history in 0.001959 seconds
run history memory usage: 137499 bytes
update filesystem C:
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 736 0.000575
updated in 0.007425 seconds
update filesystem D:
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 740 0.000814
updated in 0.001293 seconds
update filesystem F:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 744 0.000681
updated in 0.001127 seconds
loaded db in 3.977075 seconds
_DB_WAIT: _db_load_successful_proc waiting...
_DB_WAIT: _db_load_successful_proc waited 0.000726 seconds
start all monitors (3)
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 756 0.000235
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
search '' filter ''
term 0000000004093240, flags: 0140, next: 0000000000000000, notnext: 00000000000
00000
folderop: 0, fileop: 0, term:
new thread (1)
opened 752 0.000224
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 780 0.000327
waiting for 4 handles, isdelay 0...
found 48104 folders, size 394504, db search time taken: 0.000339 seconds
found 246653 files, size 2036016, db search time taken: 0.001312 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000684 seconds
new thread (2)
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000137 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002322 seconds
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000490d9c
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.001522 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002430 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000228 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002583 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000993 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001354 seconds
next update at 24/06 6:46
scanning G:\...
scan completed in 0.001346 seconds
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000000000
enter folder update
leave folder update
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000781 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.003057 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000189 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000788 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000102 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001771 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000352 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001286 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000137 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000887 seconds
waiting for 3 handles, isdelay 1...
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
_DB_WAIT: db_get_result_count waiting...
updated in 0.000142 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: db_get_result_count waited 0.001946 seconds
waiting for 4 handles, isdelay 0...
find uncached items...
sorting by path...
multithreaded sort: items 294736, ideal threads 5, actual threads 4
new thread (3)
new thread (4)
new thread (5)
caching...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
WM_ACTIVATE 0000000000200000 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000000000
WM_ACTIVATE 0000000000200001 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000000000
_DB_WAIT: db_get_result_count waiting...
sorting cache...
multithreaded sort: items 294759, ideal threads 5, actual threads 4
finished sort, time taken 265.966565 seconds
_DB_WAIT: db_get_result_count waited 251.583728 seconds
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000490d9c
update filesystem C:
_DB_WAIT: db_get_result_count waiting...
updated in 0.955757 seconds
_DB_WAIT: db_get_result_count waited 0.953640 seconds
waiting for 4 handles, isdelay 0...
next update at 24/06 6:50
scanning G:\...
scan completed in 0.001224 seconds
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000490d9c
enter folder update
leave folder update
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.026904 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001191 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000000000
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.002829 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.003038 seconds
waiting for 4 handles, isdelay 0...
multithreaded sort: items 246728, ideal threads 4, actual threads 4
finished sort, time taken 0.302931 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000650 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.023348 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000936 seconds
waiting for 4 handles, isdelay 0...
find uncached items...
sorting by path...
caching...
sorting cache...
multithreaded sort: items 294833, ideal threads 5, actual threads 4
finished sort, time taken 0.178422 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000896 seconds
finished sort, time taken 0.000714 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000956 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.023646 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002204 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.009363 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001310 seconds
multithreaded sort: items 246728, ideal threads 4, actual threads 4
finished sort, time taken 0.295592 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000664 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 0000000000200000 0000000000000000, lastfocus 0000000000490d9c, curre
nt focus 0000000000000000
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.025695 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001491 seconds
waiting for 4 handles, isdelay 0...
I closed the debug, Opened another debug and did a size sort again, which was incredibly fast at 15 sec.
Fast sort.

Code: Select all

load localization
load everything icon
create mutex
bookmarks
set hook
create tray
db_load
new thread (0)
_db_filesystem_add 0: 0, 00000000002bcee0
_db_filesystem_add 1: 0, 00000000002bcf40
_db_filesystem_add 2: 0, 00000000002bcfa0
_db_filesystem_add 3: 2, 00000000002df580
SHChangeNotifyRegister: 1968644 36867 1 0
bind to family 23, protocol 6, socktype 1
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 712 0.000192
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 712 0.000144
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 712 0.000143
bind to family 2, protocol 6, socktype 1
ETP server online.
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000000000, curre
nt focus 0000000000000000
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 736 0.000597
find recent changes on C:
enter setfocus
leave setfocus
invalidate
enter main loop
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 736 0.000406
find recent changes on D:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 736 0.000877
find recent changes on F:
loaded 8519 of 266396 changes in 2.941142 seconds
recent changes memory usage: 464159 bytes
loaded 136 run history in 0.002082 seconds
run history memory usage: 137499 bytes
update filesystem C:
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 744 0.000718
remove subfolders and files from _asw_aisI.tm~a07744
removed 0 subfolders and 0 files from _asw_aisI.tm~a07744 in 0.009257 seconds
remove subfolders and files from _asw_aisI.tm~a06572
removed 0 subfolders and 0 files from _asw_aisI.tm~a06572 in 0.010216 seconds
remove subfolders and files from _asw_aisI.tm~a08176
removed 0 subfolders and 0 files from _asw_aisI.tm~a08176 in 0.009234 seconds
flush remove folders : count 6
updated in 0.113486 seconds
update filesystem D:
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 748 0.000776
updated in 0.001286 seconds
update filesystem F:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 752 0.000587
updated in 0.001045 seconds
loaded db in 3.134313 seconds
_DB_WAIT: _db_load_successful_proc waiting...
_DB_WAIT: _db_load_successful_proc waited 0.000728 seconds
start all monitors (3)
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 760 0.000298
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
search '' filter ''
opened 764 0.000555
term 00000000034e5270, flags: 0140, next: 0000000000000000, notnext: 00000000000
00000
folderop: 0, fileop: 0, term:
new thread (1)
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 784 0.002481
found 48101 folders, size 394504, db search time taken: 0.000238 seconds
waiting for 4 handles, isdelay 0...
found 246367 files, size 2036016, db search time taken: 0.001519 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000606 seconds
next update at 24/06 6:53
scanning G:\...
new thread (2)
scan completed in 0.000747 seconds
new thread (3)
enter folder update
leave folder update
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000372 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001393 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.001549 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002579 seconds
waiting for 4 handles, isdelay 0...
find uncached items...
sorting by path...
multithreaded sort: items 294445, ideal threads 5, actual threads 4
new thread (4)
new thread (5)
caching...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
sorting cache...
multithreaded sort: items 294468, ideal threads 5, actual threads 4
finished sort, time taken 31.705616 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000810 seconds
update filesystem C:
updated in 0.068383 seconds
waiting for 4 handles, isdelay 0...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001369 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.026567 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002403 seconds
waiting for 4 handles, isdelay 0...
multithreaded sort: items 246367, ideal threads 4, actual threads 4
finished sort, time taken 0.249670 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000619 seconds
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000210cd4
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000000000
WM_ACTIVATE 0000000000200000 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000000000
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.012004 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001953 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.016950 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002956 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000258 seconds
waiting for 4 handles, isdelay 0...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002110 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000223 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.004303 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000251 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002932 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.003013 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000200 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.013187 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000914 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000069 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000826 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.002184 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000617 seconds
waiting for 4 handles, isdelay 0...
next update at 24/06 6:54
scanning G:\...
scan completed in 0.001550 seconds
enter folder update
leave folder update
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.021616 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000909 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.007923 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000217 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000599 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000756 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.002518 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000739 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.025495 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000224 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.004570 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000731 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 0000000000200001 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000000000
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000210cd4
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.012061 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001752 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.008798 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001432 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.008364 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002188 seconds
waiting for 4 handles, isdelay 0...
find uncached items...
sorting by path...
caching...
sorting cache...
multithreaded sort: items 294470, ideal threads 5, actual threads 4
finished sort, time taken 0.180822 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000802 seconds
finished sort, time taken 0.000618 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000992 seconds
multithreaded sort: items 246369, ideal threads 4, actual threads 4
finished sort, time taken 0.263909 seconds
_DB_WAIT: db_get_selection_count waiting...
_DB_WAIT: db_get_selection_count waited 0.000711 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.011450 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001213 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.020202 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000566 seconds
WM_ACTIVATE 0000000000200000 0000000000000000, lastfocus 0000000000210cd4, curre
nt focus 0000000000000000
waiting for 4 handles, isdelay 0...
Hope this serves some purpose...
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

Thanks for the debug output.

Since Everything does not index sizes and dates, this information must be gather from the disk.

You should see disk activity the first time your sort by size, date or attributes.
Everything does cache this information while the window is opened.
Windows will also cache this information, so closing the search window and reopening it and performing a sort will be quite fast.
Windows will throw out this cache if it's old or low on memory.

There does seem to be an issue with live locking in 657b which could be causing the sort to do nothing for an extended period of time.
I hope to post a fix soon.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

Since Everything does not index sizes and dates, this information must be gather from the disk.
You should see disk activity the first time your sort by size, date or attributes.
Everything does cache this information while the window is opened.
I am not too sure I have seen the disk activity in Sorting in 649b , which always yielded fast results even when I ran it immediately on starting ET.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

So it appears , ET will always read the disk if a query or sort is made , immediately at the start of ET.During those times , I checked the Disk Read Speed from PE , which put it at around 350 to 450 K . Could that be enhanced or it has its limitation because of the number of files it has to read rather than a bulk file.
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

So it appears , ET will always read the disk if a query or sort is made , immediately at the start of ET.
Yes, this is the expected behavior.
It is currently not very fast.

I have implemented basic support for reading this information directly from the MFT on NTFS volumes, however this is still in early alpha, I hope to add this in a future release.

I want to rewrite the db code so Everything will index this information instead of caching it when displayed, sorting or searching with a size: query.

As for folder indexes, they will always be slow to index.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

Just a suggestion
If instead of closing ET , I minimise to the Taskbar after a size sort say , any number of sorting and query is immediate thereafter. But if I closed it and were to be recalled from the systray , there is a slight delay in further query or sort with CPU usage. Can the connection with the cache be maintained even if it is closed to the systray if it is technically possible , because I do not see any significant amount of RAM difference say 10MB in XP between those two states.Perhaps at least as a choice....
vsub
Posts: 474
Joined: Sat Nov 12, 2011 11:51 am

Re: Sort

Post by vsub »

When you close the window,the window is destroyed and when you call it again,the whole window with every element is recreated,the last search(if the option is enabled)is automatically added to the search and a search is performed.

One possible solution for this would be to hide the window rather that destroying it(that way everything wont have to do anything...the icons don't need to be loaded again and the sort order will be like the last time without having to wait for everything to sort the list again)
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

But again plain hiding will impose a compromise on Home page..? :roll: Then while closing/hiding the sort should be set to Name so that it opens with a clean slate.
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

I have added the ini option:

Code: Select all

hide_on_close
for the next beta update.

When this is set to 1 and the window is closed, instead of being closed the window is hidden.
The window can be shown by starting Everything.exe or opening a search window from the tray icon.

Showing a hidden window will not open the home page.
vsub
Posts: 474
Joined: Sat Nov 12, 2011 11:51 am

Re: Sort

Post by vsub »

Nice...this will be useful for something I wanted to do with Autohotkey(don't remember what was it right now :p )but I couldn't because the window was destroyed when I close it.
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

I just checked with some filters , modifiers and then called the Home page thru a bookmark which is loaded default with no accessories. Still the cache is maintained and the queries are immediate. But just for information I do have come across certain applications (like Syncback -SE) which on "Window close" do a little more of work like say exporting some inf files and then close. So I was wondering if the close button could make ET invoke the home page and then hide so that it appears nothing has changed. By the way the bookmark route is also fine....
nagan
Posts: 302
Joined: Thu Apr 18, 2013 11:44 am

Re: Sort

Post by nagan »

Just curious..
I open Window A and browse ETP files.
Then Window B , do some sort and keep it just ready for immediate query and sort results.
Then Window C , where I browse some files with filters and modifiers on.

Also I find In Window C which opens after "B" were I do some query it is a high speed , high CPU search when attempted for the first time.

So if I close the windows in the order A B C or C B A , how do they open from the systray. If
close is what is intended , then I need not expect all the windows to open. If ET could identify which window was the most linked to the cache and opens that , might be ideal?
void
Developer
Posts: 16748
Joined: Fri Oct 16, 2009 11:31 pm

Re: Sort

Post by void »

Also I find In Window C which opens after "B" were I do some query it is a high speed , high CPU search when attempted for the first time.
Each window has it's own cache.
So if I close the windows in the order A B C or C B A , how do they open from the systray
The window with the last focus will be shown/unhidden from the system tray.
If ET could identify which window was the most linked to the cache and opens that , might be ideal?
The user might want the cache of the ETP connection from window A?
No cache will be lost when hiding/un-hiding windows, so it shouldn't matter.
Post Reply