[Bug 2578] file write performance very poor due to dup+write+close

[Wine Bugs]

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

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|file write performance over |file write performance very
                   |NFS very poor due to        |poor due to dup+write+close
                   |dup+write+close             |

------- Additional Comments From [e-mail]  2005-04-10 13:55 -------
I haven't raised the issue on wine-devel hoping that someone else with more
energy would magically appear and champion it for me.  no surprise that that
didn't happen. ;)  as it is, i just keep applying my patch to wine anytime i get
a new version.

i recently tested it on a local disk, the extreemly poor performance was not NFS
related it happens on any filesystem.

I have no need for "correct" windows file locking semantics in my own limited
use.  I wonder how many uses of wine actually do?  i'd expect most wine users to
be running a single application per wine instance if they're running more than
one thing at all in the first place.

Regardless one way around that would be to turn my patch into an option (command
line or config file) as to wether file locking should be done correctly at the
expense of extreemly slow file writes.