6.90 - 5524 - how to monitor progress of LOCAL search?

[stavros]

Hi,
Using build 6.90 - 5524 and I'm doing a LOCAL search across my spool.
Spool is about 400 groups, about 3TB of data.

It is taking quite a while, how can I monitor the progress of the LOCAL search?

All I am seeing is a small blue bar shuttleing across the bottom of the search window, with no results found.
I can't see any other feedback as to what is going on, which GoG/group is being currently searched
or anything else useful in the DEBUG log.

I'm not really worried about the time taken, but I would like to know more about what is actually happening

regards
Stavros.

[BZee]

I use Sysinternals' Process Monitor {ProcMon}. Under "Filter" set "Display entries matching these" to 'Process Name' 'is' "NewsbinPro64.exe" then 'include' and click Add and OK.
Again under "Filter" click "Save Filter..." and enter a name - I use "Newsbin"
The 3rd icon {magnifier} starts/stops monitoring and the 5th {paper being erased} clears the list of event logged

[stavros]

Thanks BZee, does that show which GoG and / or group is currently being searched?

Later:
I see that it does, I switched on 'autoscroll' (4th Icon) and I can follow the paths changing as it works it's way
through the spool.

Thanks BZee - a good workaround

[Quade]

The problem is Newsbin doesn't know the total counts in each group until it counts them which is in itself fairly time consuming.

So to get a real progress bar, I'd have to count the contents of each group, note it, then during the search count up the number of records as it goes. It's probably doable.

[stavros]

Hi Quade,

I'd be happy with some text in the status bar (where the scrolling blue bar is) at the bottom of the search window saying something like:

currently searching <group name>, # of total # groups

getting updated when it starts searching a new group
(EDIT* and maybe dumped to the debug log as it gets updated?).

It would be nice if there were more details, but anything showing progress would be better that the total lack of feedback at the moment.
I just did a search that bought back about a hundred rows from my spool, but it took over 90 minutes before the first row was returned,
and another 60 before the search completed.

Maybe something in the debug log at the end of the search saying what the search string was, how many groups searched, how many hits found, any other easily acquired stats?

regards
Stavros