https://bugs.winehq.org/show_bug.cgi?id=57289
Bug ID: 57289 Summary: Performance degradation after LFH Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs@winehq.org Reporter: rikul@inbox.ru Distribution: ---
In one of my applications, there is a performance degradation in a specific scenario after LFH. I still can’t localize the problem to send you the block of code where the tool experiences performance issues.
Are you aware of any known issues related to this? The main part of the degradation occurs in the LFH group release section.
https://bugs.winehq.org/show_bug.cgi?id=57289
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- LFH meaning "low fragmentation heap"?
https://bugs.winehq.org/show_bug.cgi?id=57289
--- Comment #2 from BugSeeker rikul@inbox.ru --- Yes, LFH is Low Fragmentation Heap. In that scenario, closing the group_release (which has the memory leak) restores the performance numbers to their previous, better levels. Are you familiar with this? Are there any known issues?
https://bugs.winehq.org/show_bug.cgi?id=57289
--- Comment #3 from BugSeeker rikul@inbox.ru --- I mean closing the call to the group_release() function for the experiment to identify where the performance is lacking
https://bugs.winehq.org/show_bug.cgi?id=57289
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- Sorry, I'm not familiar with this, just looking for clarification. Without being able to reproduce and profile that could be difficult.
-
WineHQ Bugzilla