Announcement

Collapse
No announcement yet.

Resource Usage Observation...

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Resource Usage Observation...

    There seems to be a general concern about PSU2018 performance... There are many comments on how other tools do not have the same issues... I really don't have any issues, but my OCD with problem solving kicks in and I start looking around...

    ​I started playing with Affinity Photo as (hopefully) an example of a generally modern code set (less legacy support) to look for differences... Honestly, I am not sure what to look for... but I did find something interesting. Using Affinity to do similar edits as PSU2018, with Affinity, it seems my NVidia GPU, Intel GPU and Intel CPU all see some sort of activity with any edit. Typically 40%, 50%, and 40% respectively.

    With ACDSee... it seems that only the NVidia GPU and Intel CPU are used. Maybe 25% and 20%, respectively.
    .

    This got me to thinking...
    ​Is Affinity a resource hog that needs these other helpers?

    ​Is it possible PSU2018 could be assisted by use of further available resources in higher-end machines?
    (At the expense of forcing higher minimum hardware requirements)

    ​How does having a DAM, Develop, and Edit (PSU208) development compare with only having Develop and Edit (Affinity)?

    Helper apps add to my annual software cost.




  • #2
    It doesn't seem to use any more resources than anything else. It's just ridiculously slow to load. It's up to something in the background.

    Edit: it's looking at every file in the folder of the image you're opening. It also spends 3-4 seconds trying to get in touch with MobileSync through Commander. I can't believe what a piece of **************** this program has become.
    Last edited by Klause Kunnenunt; 12-31-2017, 04:51 AM.

    Comment


    • #3
      You and I have different perspectives as our experiences are very different. I am glad that I do not suffer the same issues that you see. I apologize for not being able to offer any suggestions that work for you.

      Comment


      • #4
        Maybe you can makes sense of this. Why do you think it pauses and does nothing for 14 seconds while opening an image? See lines 4-5:

        41:35.9 ACDSeeUltimate2018.exe 16192 RegQueryKey HKCU
        41:35.9 ACDSeeUltimate2018.exe 16192 RegOpenKey HKCU\Software\ACD Systems\ACDSee Ultimate\110
        41:35.9 ACDSeeUltimate2018.exe 16192 RegQueryValue HKCU\Software\ACD Systems\ACDSee Ultimate\110\ModeWndPos
        41:35.9 ACDSeeUltimate2018.exe 16192 RegCloseKey HKCU\Software\ACD Systems\ACDSee Ultimate\110
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryKey HKLM
        41:49.3 ACDSeeUltimate2018.exe 16192 RegOpenKey HKLM\Software\ACD Systems\ACDSee Ultimate\110\LClient
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryValue HKLM\SOFTWARE\ACD Systems\ACDSee Ultimate\110\LClient\lng
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryValue HKLM\SOFTWARE\ACD Systems\ACDSee Ultimate\110\LClient\lng
        41:49.3 ACDSeeUltimate2018.exe 16192 RegCloseKey HKLM\SOFTWARE\ACD Systems\ACDSee Ultimate\110\LClient
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryKey HKCU
        41:49.3 ACDSeeUltimate2018.exe 16192 RegOpenKey HKCU\Software\ACD Systems\ACDSee Ultimate\110\EN\CustomHotKeys\Viewer\BCGKeyboard-0
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryValue HKCU\Software\ACD Systems\ACDSee Ultimate\110\EN\CustomHotKeys\Viewer\BCGKeyboard-0\Accelerators
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryValue HKCU\Software\ACD Systems\ACDSee Ultimate\110\EN\CustomHotKeys\Viewer\BCGKeyboard-0\Accelerators
        41:49.3 ACDSeeUltimate2018.exe 16192 RegQueryValue HKCU\Software\ACD Systems\ACDSee Ultimate\110\EN\CustomHotKeys\Viewer\BCGKeyboard-0\Accelerators
        41:49.3 ACDSeeUltimate2018.exe 16192 RegCloseKey HKCU\Software\ACD Systems\ACDSee Ultimate\110\EN\CustomHotKeys\Viewer\BCGKeyboard-0

        Comment


        • #5
          Sorry, been out of town for a while... but, I am back and a bit curious...

          ​I tried taking a harder look at these two entries.... 41:35.9 ACDSeeUltimate2018.exe RegCloseKey HKCU\Software\ACD Systems\ACDSee Ultimate\110
          41:49.3 ACDSeeUltimate2018.exe RegQueryKey HKLM

          Seems to have something to do with the time from closing the Registry Key then querying the same registry.


          First I am wondering thought through things that could take time that could add delay in the closing process.
          I had to take a look about closing registry keys and found these references...
          https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
          http://www.vbforums.com/showthread.p...nd-RegCloseKey
          https://serverfault.com/questions/26...s-in-windows-7
          Closing the registry seems to requires, finishing the registry write, flushing the cache, then actiually closing the threads.

          Then, I thought about delays caused by quering the registry. I found these interesting threads
          https://social.msdn.microsoft.com/Fo...elopmentissues
          https://connect.microsoft.com/Visual...details/780437
          https://www.reddit.com/r/techsupport...w_ssd_windows/

          I poked around in the following direectory for a while and did not find anything interesting... but then again, my system seems to work OK
          C:\Users\[username]\AppData\Local\ACD Systems.

          Thoughts....
          * Maybe the root cause of the problem is the -extreme- reliance on registry operations.
          * We really don't know what is happening in that 14 seconds, other than there is lots of things happening between issuing the registry close and the first registry read. It could be the registry taking a long time to close. It could be a long time to query the registry
          * As some queries work on root keys, larger registries may impact the time. I guess it is possible reducing the number of programs in the computer is one possibility, but that to me that is not a fix!!
          * One of the threads suggest interference with drivers while accessing the registry... sigh.
          * To fix this entirely, seems to require a programatic change relative to one or more possible triggers that us mere users can't change.
          * Worse yet, it certainly seems that not all istallations have these triggers.

          My personal OCD does not like the constant read/writes to the registry for day-to-day operational use... but that is a longer story


          Going a step further, I decided to see what changes in the registry when ACD is started by checking the registry changes that happen when initially launching ACD. Here is the list
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\HistPaths=
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\FolderExpandState9=1
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\ViewFilterSavedFolderPIDLArraySize=26 4
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\ViewFilterSavedFolder=
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort00=1349276960
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort01=32764
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort02=7
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort03=7
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort04=0
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort05=-24737910
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort06=6357059
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort07=6357108
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\BurnBasket\Columns\Sort08=7274604
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\InTouch2\lrt=ösZZ
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\LClient\scd=Z4HVs37Y7LMtJfxfO27bfWwIR YCHlVIujVxOAQdUAHdI2mSGqhkdpQ==
          HKEY_CURRENT_USER\Software\ACD Systems\ACDSee Ultimate\110\LClient\spd=IQgX9w6dM4jo1b4drykjr4adg ohxCJHD0ESgzibTaAA=
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.nef\UserChoice\ProgID =ACDSee Ultimate 2018.nef
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.tif\OpenWithList\MRUL ist=jhifabcdeg
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:0000000000090D8E
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:0000000000090D8E\VirtualDesktop=
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:000000000009182A
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:000000000009182A\VirtualDesktop=
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:00000000000C05DA
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:00000000000C05DA\VirtualDesktop=
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:00000000002B07DC
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\SessionInfo\3\ApplicationViewMa nagement\W32:00000000002B07DC\VirtualDesktop=
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Search\RecentApps\{06912520-B5A8-4F42-828D-70A43A6300F2}\LastAccessedTime=~»Ç±ŒÓ
          HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Search\RecentApps\{06912520-B5A8-4F42-828D-70A43A6300F2}\LaunchCount=10

          ​It seems ACD searches the burn basket and reconfirs some file associations. There is also the intouch, scd, and the spd hash that seems to be license related


          ​I do not see a smoking gun, but there is definitely a lot going on.

          Comment

          Working...
          X