Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

desync when server saves game (on slow hardware) #52

Closed
DorpsGek opened this issue Feb 9, 2006 · 4 comments
Closed

desync when server saves game (on slow hardware) #52

DorpsGek opened this issue Feb 9, 2006 · 4 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Feb 9, 2006

tokai opened the ticket and wrote:

I report this problem in name of someone else (bigfoot). I don't have such (slow) hardware myself and can't reproduce therefore.

"512x512 map, 3 players, 300MHz P2 server (Linux, 0.4.5)... The game autosaves every month, and that sometimes takes so long that a few players get disconnected with "desync" error.

Moved the server over to the Peg1 (PPC/G3 @ 600MHz), no problem anymore

...

The whole game freezes on all clients while waiting for the server to save"

Maybe someone else can reproduce.

regards,
tokai

Reported version: 0.4.5
Operating system: Linux


This issue was imported from FlySpray: https://bugs.openttd.org/task/52
@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 9, 2006

tokai wrote:

Actually i thought threaded saving is used on linux and this should avoid such freeze/delay.. but it seems it doesnt?


This comment was imported from FlySpray: https://bugs.openttd.org/task/52#comment109

@DorpsGek
Copy link
Member Author

Bjarni wrote:

OpenTTD can be compiled without threaded saving since win95 or something didn't support it the way we did it. Maybe the binary got compiled singlethreaded by accident. I have no way to test that theory so somebody else will have to do that. Another reason could be that the CPU gets so overloaded that all processes get so delayed that this happens.


This comment was imported from FlySpray: https://bugs.openttd.org/task/52#comment124

@DorpsGek
Copy link
Member Author

Darkvater wrote:

From r2391 threaded saving has been disabled for the server, but I don't see anything against enabling it again. Although it won't help too much on an old PC, your best bet is to disable autosave for the server.


This comment was imported from FlySpray: https://bugs.openttd.org/task/52#comment246

@DorpsGek
Copy link
Member Author

TrueBrain closed the ticket.

Reason for closing: Fixed

Thread saving on a server is a bad bad idea for various of reasons. So keeping it off for now seems like a very good idea. Closing bug.


This comment was imported from FlySpray: https://bugs.openttd.org/task/52

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant