[Bug 59440] New: NTSync doesn't work very well in ONGEKI Re:Fresh.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59440

            Bug ID: 59440
           Summary: NTSync doesn't work very well in ONGEKI Re:Fresh.
           Product: Wine-staging
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail]
      Distribution: ---

Created attachment 80422
  --> http://bugs.winehq.org/attachment.cgi?id=80422
Kernel: 6.19.2-1-MANJARO

I looked at perf.data, and 40% of the time was spent on the function
NtWaitForSingleObject, which is obviously abnormal.  
I checked the locks, and one unnamed lock had an average wait time of 2.33
seconds. Since I can't upload more than two attachments, the lock report for
that line is as follows:  

                Name   acquired  contended     avg wait   total wait     max
wait     min wait 

                         600487     600487      3.88 us      2.33 s      91.82
us       568 ns 
                             67         67    193.90 us     12.99 ms    480.07
us      2.38 us 
           rcu_state         17         17      2.36 us     40.13 us      2.93
us      1.67 us 
                             13         13      3.13 us     40.67 us      4.61
us      1.80 us 
           rcu_state          3          3      2.52 us      7.57 us      3.02
us      2.24 us 
                              2          2      1.58 us      3.16 us      1.80
us      1.36 us 
        jiffies_lock          2          2      2.24 us      4.47 us      2.33
us      2.15 us 
                              1          1      1.90 us      1.90 us      1.90
us      1.90 us 
                              1          1      1.47 us      1.47 us      1.47
us      1.47 us 
                              1          1      3.23 us      3.23 us      3.23
us      3.23 us 
                              1          1      7.11 us      7.11 us      7.11
us      7.11 us 
                              1          1      7.52 us      7.52 us      7.52
us      7.52 us

Each lock was contended once, which seems to be caused by some sort of
conflict.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 59440] NTSync doesn't work very well in ONGEKI Re:Fresh.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59440

Zeb Figura <[e-mail]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |-unknown
            Product|Wine-staging                |Wine

--- Comment #1 from Zeb Figura <[e-mail]> ---
(In reply to admin from comment #0)
> I looked at perf.data, and 40% of the time was spent on the function
> NtWaitForSingleObject, which is obviously abnormal.

It might be and it might not be. perf can be very misleading especially when
you're dealing with a situation where symbols are missing.

What's the actual performance characteristics of the game? How does it perform
with server-side synchronization, with ntsync, and (if you tested) with esync
or fsync?
> I checked the locks, and one unnamed lock had an average wait time of 2.33
> seconds.

Looks like you're misreading—the *total* wait time is 2.33 seconds (since the
lock is taken many many times), the average wait time is only 3.88 µs.
> Since I can't upload more than two attachments, the lock report for
> that line is as follows:

You can upload extra attachments in a following comment. Or archive them.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.