blocks|key|5684024|text|如果我一行回答。服务器将会爆炸。因为网络活动和游戏逻辑处于同一线程中。正如您所提到的，您将需要高网络使用率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5684025|如果你看看F#的话，我真的很喜欢。它有你需要的所有东西。据我所知是从问题中得到的。很少有东西像集合变化一样，异步在语言中是默认的。即使是Nodejs，它也值得一试。但同样，这完全取决于需求。虽然我试着解释一些关键字，这可能会帮助你做出决定。|offset|length|5684026|非阻塞:这意味着线程在事件时不会被阻塞。它不会等待函数等待另一个函数执行。但这并不意味着你不能阻止它。在任何情况下，它都是单个线程。|5684027|Async:有点像这样。但在C#+5中，async附带了关键字，所以你不需要在编程中做线程部分。|5684028|并行处理:在游戏开发中，并行处理非常重要。现在，你可以使用多线程或者只使用TPL。|5684029|对于基于UI的游戏(其中有许多对象)，我强烈建议您将处理线程和UI线程分开，以改善用户体验。否则，当您处理数据时，FPS将会关闭。|5684030|如果需要任何进一步的信息，请告诉我。|5684031|如果你不注意服务器，它就不会宕机。|5684032|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tryfsharp.org/|1|http://nodejs.org/|2|http://msdn.microsoft.com/en-us/library/dd460717.aspx^0|0|5|2|0|1W|6|1|0|0|0|11|3|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]|$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|L|3|M|5|6|7|1H|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1I|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|U|V|W|A|$X|10]]|11|$5|U|V|W|A|$X|12]]]]

If I give answer in one line. Server will explode. As network activity and game logic is in same thread. And as you have mentioned you will be needing high network usage.

I seriously like that if you have a look to <a href="http://www.tryfsharp.org/" rel="nofollow">F#</a>. It has all the things that you needed. As far as I got it from question. And few things are like collection change, and async is by default in language. Even <a href="http://nodejs.org/" rel="nofollow">Nodejs</a> it is also worth trying. But again it all depends on requirement. Though I try to explain few keywords that may help you to take decision.

Non-blocking : It means thread will not be block on events. It will not wait for function to wait for another function to execute. But that doesn't mean you can't block it. In any case it is a single thread.

Async: It is some what like that. But in C# 5 async comes with keyword so you don't have to do threading part of programming. 

Parallel Processing: In game development parallel processing is important. Now, that you can do with multiple thread or just use <a href="http://msdn.microsoft.com/en-us/library/dd460717.aspx" rel="nofollow">TPL</a>.

In the case of UI based (where there are many objects) game I highly recommended that you separate processing thread and UI thread to improve user experience. Else FPS will go down while you are processing data. 

Let me know if any further information needed.

Server will not go down if you take little care of it.

blocks|key|688736|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|688737|服务器会爆炸吗？|blockquote|688738|688739|688740|是的，你可能会遇到问题(“爆炸”)，因为异步的东西是在不同的线程上运行的(即使你没有显式创建那个线程)，并且它可能会与你的主线程同时访问一个共享对象(world)。许多数据结构(包括字典)不是为此场景设计的，可能会崩溃或返回错误的答案。|688741|典型的方法是使用锁来保护您的共享对象:在修改锁之前获取锁，做任何修改，然后释放锁。这样，一次只有一个线程访问这个世界(以及它的字典)，所以一切都保持一致。避免了爆炸。|688742|另一种方法是切换到更同步的网络形式，例如，可能避免完成处理程序，而是等待收到每个玩家的消息，然后对输入采取行动。这可以非常简单地完成，但简单的方法有缺点:任何一个速度慢的玩家都可以放慢整个过程。所以可悲的是，你可能不得不以某种方式处理一些复杂性。|688743|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|R|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|S|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|T|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|U|7|@]|8|@]|9|$]]]|M|$]]

<blockquote>
 will the server explode?
</blockquote>

Yes, you can run into problems ("explode") because the async stuff is running on a different thread (even though you didn't create that thread explicitly) and it might access a shared object (world) at the same time as your main thread. Many datastructures (including the Dictionary) are not designed for this scenario and might crash or return the wrong answer.

The typical approach is to use locks to protect your shared objects: take the lock before modifying it, do whatever modification, and then release the lock. This way, only one thread at a time accesses the world (and its dictionary) and so everything remains consistent. Explosion averted.

Another way would be to switch to a more synchronous form of networking, perhaps for example avoiding completion handlers and instead waiting to hear from each of the players, and then acting on the inputs. This can be done very simply, but the simple way has drawbacks: any one slow player can slow the whole thing down. So sadly you're probably going to have to deal with some complexity, one way or another.

blocks|key|5684139|text|如果在同一线程上，则不是。如果你在一个线程上做所有提到的工作，那么就不会有问题。然而，如前所述，如果您正在跨线程访问“共享”对象实例，那么是的，将会有一个问题，并且将需要锁定(使用"lock(){...}“块)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5684140|随着用户数量的增加，您必须关注生成的线程数量，或者如果对传入请求使用非阻塞事件模型，则需要关注事件消息的数量。|5684141|在不同的，但相关的注释中，请关注这个基于C#的MMO服务器(支持脚本)：https://dreamspace.codeplex.com/+-它可能很快就会对MMO游戏创建者有很大的帮助(默认情况下将支持Construct2)。|offset|length|5684142|entityMap|0|LINK|mutability|MUTABLE|url|https://dreamspace.codeplex.com/^0|0|0|10|W|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If on the same thread, then no. If you are doing all the work mentioned on a single thread, then there's no issue. However, as stated, if you are accessing a "shared" object instance across threads, then yes, there will be an issue, and locking will be required (using a "lock(){...}" block).

As your user base increases, you will have to keep an eye on the number of threads generated, or event messages if using a non-blocking event model for incoming requests.

On a different, yet related note, keep an eye on this C# based MMO server (with scripting support): <a href="https://dreamspace.codeplex.com/" rel="nofollow">https://dreamspace.codeplex.com/</a> - it may become a big help to MMO game creators very soon (will support Construct 2 by default).

If I have 1 thread for my MMORPG server running a async socket and async packet handler, and in that 1 thread I have a static World that contains all entities in the game.

Would there be any threading issues if say, the async packet handler recieves an Attack message, resulting in a search of the entities in the world to figure out the target. 

At the same time the static World Proc method is increasing the size of the Dictionary containing the monster entities adding extra monsters that spawned. 

If this is all on the same thread, will the server explode?

C# Server for MMORPG, thread-safety with async

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果我的MMORPG服务器有一个运行异步套接字和异步数据包处理程序的线程，在这一个线程中，我有一个包含游戏中所有实体的静态World。如果异步数据包处理器接收到攻击消息，导致搜索世界上的实体以确定目标，是否会有任何线程问题。同时，静态的World Proc方法增加了包含怪物实体的字典的大小，增加了产生的额外怪物。如果这...

问C#服务器，异步线程安全
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C#服务器，异步线程安全EN