MinHook库性能问题 [英] MinHook Library Performance Issue
问题描述
你好.希望这个问题对您有帮助.
我正在考虑使用您的MinHook库来替代NtHookEngine库，以实现JauntePE项目的api挂钩要求的64位使用.我想改用您的库，因为它解决了我遇到的两个问题，而您在MinHook文章中提到了这一点，即NtHookEngine不使用5字节跳转，也没有解决修正移动代码相对地址的需要. >
但是我在性能上有问题.对于同一个应用程序，32位版本只需4毫秒即可应用所需的64个钩子.但是64位版本需要5000毫秒或更长时间.我想知道您是否知道性能瓶颈在哪里?我假设它在内存块分配中的某个地方，试图在其中定位可用的继电器"块，但是我不确定，因为我无法调试64位应用程序. br/>
您在这方面给我的任何帮助将不胜感激！
最好的问候，
Darrell L(又名redllar)
Hello there. I hope this question finds you well.
I''m looking into using your MinHook library as a replacement for the NtHookEngine library for 64 bit use of my JauntePE project''s api hooking requirements. I''d like to use your library instead since it solves the two problems I ran into and you mentioned in your MinHook article, i.e., NtHookEngine not using 5 byte jumps and not addressing the need to fixup moved code relative addresses.
But I''m having a problem with performance. With the same app, the 32 bit version takes only 4 milliseconds to apply the 64 hooks it needs. But the 64 bit version takes 5000 milliseconds or worse. I was wondering if you had any idea where the performance bottleneck might be? I''m assuming it''s somewhere within the memory block allocation where it''s attempting to locate a usable "relay" block, but I''m not sure since I can''t debug the 64 bit app.
Any help you could give me in this area would be greatly appreciated!
Best regards,
Darrell L (aka redllar)
推荐答案
您的意思是这篇文章
—SA
Do you mean this article, MinHook - The Minimalistic x86/x64 API Hooking Library[^]?
Is so, you should better load the referenced page and click "New Message" below the article page to ask your questions. The author of the article will get e-mail notification and a chance to answer them.
—SA
请将此邮件发布在 Tsuda Kageyu [
Please post this in the message board of the MinHook - The Minimalistic x86/x64 API Hooking Library[^] article. The author Tsuda Kageyu[^] will help you if you have any problems with the code of that article.
Thanks for your cooperation!
这篇关于MinHook库性能问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
