is that right? it would seem that moving the lock to a higher level would be a good place to start. It looks like this is getting called for every file on the disk, for every file type in the types dialog. it looks like it's doing this in an extremely inefficient manner: the 'lock xadd' in the following loop is causing the CPU to purge cache & sync in a tight loop. Ok, one thread seems to spend a considerable amount of time looping through the items in the 'file types' dialog. almost all of the CPU time is spent inside the defraggler64.exe code, ie. ![]() But it seems there are two threads which basically take turns pegging the core.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |