A small test of performance and variation, 1.7.0.409

tullik

A small test of performance and variation, 1.7.0.409

Test conditions and procedures:

1. Vista, RSPro v 1.7.0.409, "Raw" list and normal scan settings for Registry Cleaner

2. Observe results for an "Initial Registry Cleaner (RC) scan" (the first RC scan made after launching RSPro)

3. Observe results for several rescans (a scan made after the initial one without exiting RSPro)

4. Vista registry contained only a few errors which were to be left alone after each scan

5. Source of timing and items found would be the RC results window and Scan Report

6 Task Manager Performance window to be visible during all scans

Observations:

1. Total scans done, 2 initial scans and 18 rescans

2. Run times:
a. Initial, 89.9 and 93.5 seconds

b. Rescans, shortest = 69.8, longest = 88.8, fifteen others = from 70.0 to 74.0, seconds

c. One rescan had to be killed due to an "AppHangB1" event (windows pop-up content below after screenshot)

3. Found item counts, every scan but one listed the same 32 items

a. 2 "Useless file extension" keys in HKCU

b. 15 "File or directory does not exist" entries in HKCU keys

c. The same 15 entries in "twinned" HKUS keys ( look here for a definition of "twinning" )

d. The exception scan did not show the HKUS items

4. Performance (cpu usage):

a. Both initial scans looked like the left side graph in the screenshot

b. All the rescans looked like the right side

Conclusions and issues:

Disclaimers: sample is small; registry contained only a few errors.

1. Given the same registry content, RC has little variation in the number of items detected as errors (usually :| )

2. Issue: RC usually includes too many duplicates in the results window -- Edit: or "Sometimes does not include entries duplicated by windows." :

3. Given the same registry content, RC scan run times are very consistent (except for an "initial scan")

4. Issue: RC GUI hangs for 10-20 seconds in an "initial scan" (happens every time, but only in Vista) -- a description of the behavior will be posted to this thread a bit later.

Other information:

As the following message indicates (Fix was clicked after one more rescan was done), RSPro RC does not seem actually to use the duplicate entries shown in the list

: The registry fixing procedure is now complete. It was possible to correct 2 items out of 17, 15 items had to be removed in order to fix the problems. You can undo all the changes from the backups.

Screenshot showing an initial scan and a rescan

Shot at 2007-08-20

Content of "AppHangB1" pop-up

Description: (RC tool window)

A problem caused this program to stop interacting with Windows.

Problem signature:

Problem Event Name: AppHangB1

Application Name: RegSupremePro.exe

Application Version: 1.7.0.409

Application Timestamp: 2a425e19

Hang Signature: 3f9e

Hang Type: 0

OS Version: 6.0.6000.2.0.0.256.6

Locale ID: 1033

Additional Hang Signature 1: 01469b638a47f383627e6245d2a20ee6

Additional Hang Signature 2: 583d

Additional Hang Signature 3: b256ae3866495a655be4e4ecbd507a27

Additional Hang Signature 4: 3f9e

Additional Hang Signature 5: 01469b638a47f383627e6245d2a20ee6

Additional Hang Signature 6: 583d

Additional Hang Signature 7: b256ae3866495a655be4e4ecbd507a27

Message box from an "initial scan"

: Open With entry scan finished.

: Help file entry scan finished.

: Menu order scan finished.

: Application path scan finished.

: Font entry scan finished.

: Add / Remove software list scan finished.

: Obsolete software scan finished.

: Shared Component entry scan finished.

: File reference scan finished.

: File extension scan finished.

: Left-over software data scan finished.

tullik

tullik wrote
… 4. Issue: RC GUI hangs for 10-20 seconds in an "initial scan" (happens every time, but only in Vista) -- a description of the behavior will be posted to this thread a bit later. …

Note: In the following discussion, PT refers to both PT2007 and RSPro 1.7, since the issue exists in both progams.

This problem has been in the new registry scanning engine from the start. The main impact is on users who wish immediately to use other PT tools while the scan runs. The issue hangs all PT windows, so immediate use is not possible.

Issue characteristics (refer to the screenshot):
1. The hang shows in the left side graph. It occurs immediately and lasts during the ~15 to 20 second trough.

2. For the first ~3 seconds, no PT window responds in any way to mouse clicks.

3. During this period, per the message box, several of the shorter scan threads finish.

4. Starting at about second 4, a mouse click on any PT window causes it to lose focus.

5. At the same time, depending on where you click, windows recognizes the "not responding" condition and enters a "what to do about it" dialogue

6. The hang lasts for another 10+ seconds and breaks free when another thread shows finished in the message box.

7. The messages from the "initial scan" in the screenshot are after the screenshot.

8. The hang broke free when the red message appeared.

9. The hang does not occur during rescans in the same PT session.

Screenshot showing an initial scan and a rescan

Shot at 2007-08-20

Message box from an "initial scan"

: Open With entry scan finished.

: Help file entry scan finished.

: Menu order scan finished.

: Application path scan finished.

: Font entry scan finished.

: Add / Remove software list scan finished.

: Obsolete software scan finished.

: Shared Component entry scan finished.

: File reference scan finished.

: File extension scan finished.

: Left-over software data scan finished.

jv16

The initial scan freeze is now fixed, thank you for reporting. The fixed verson should be out today.