blocks|key|5433881|text|C#+sharps内存管理实际上非常好，所以您可以只分配所需的内容并将其放入队列中，而不是拥有一个缓冲池。一旦你使用完buffer，就让垃圾收集器来处理它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5433882|另一种选择(对应用程序知之甚少)是在获得消息时对它们进行最低限度的处理，并将它们转换为完全成熟的对象(具有优先级和所有)，然后您的队列可以通过调查正确的属性或方法集来确定它们的优先级。|5433883|如果您的消息传入太快，甚至对于最小的处理，您可能会有一个两个队列的系统。一个只是一个未处理的缓冲区队列，下一个队列是从缓冲区构建的消息对象队列。|5433884|我希望这能帮到你。|5433885|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

C# sharps memory management is actually quite good, so instead of having a pool of buffers, you could just allocate exactly what you need and stick it into a queue. Once you are done with buffer just let the garbage collector handle it.

One other option (knowing only very little about your application), is to process the messages minimally as you get them, and turn them into full fledged objects (with priorities and all), then your queue could prioritize them just by investigating the correct set of attributes or methods.

If your messages come in too fast even for minimal processing you could have a two queue system. One is just a queue of unprocessed buffers, and the next queue is the queue of message objects built from the buffers.

I hope this helps.

blocks|key|2280332|text|为什么不直接接收消息，创建一个DeviceMessage+(因为没有更好的名称)对象，并将该对象放入队列中？如果优先级很重要，那么实现一个自动处理优先级的PriorityQueue类(将DeviceMessage对象插入到队列中时按优先级顺序排列)。这似乎是一种更面向对象的方法，并且会随着时间的推移而简化优先级排序方面的维护。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2280333|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Why wouldn't you just receive the messages, create a DeviceMessage (for lack of a better name) object, and put that object into a Queue ? If the prioritization is important, implement a PriorityQueue class that handles that automatically (by placing the DeviceMessage objects in priority order as they're inserted into the queue). Seems like a more OO approach, and would simplify maintenance over time with regards to the prioritization.

blocks|key|2276683|text|我也在做类似的事情。我有从MTA线程传入的消息，需要在STA线程上提供服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2276684|我使用了一个BlockingCollection+(并行fx扩展的一部分)，它由几个STA线程监控(可配置，但缺省为xr+*内核数量)。每个线程都会尝试从队列中弹出一条消息。它们要么超时并重试，要么成功弹出一条消息并为其提供服务。|offset|length|2276685|我已经将它与perfmon计数器连接起来，以跟踪空闲时间、作业长度、传入消息等，这些可以用来调整队列的设置。|2276686|您必须实现一个自定义集合，或者可能扩展BC，以实现队列项优先级。|2276687|我以这种方式实现它的原因之一是，据我所知，queueing+theory通常偏爱单行、多服务器(为什么我觉得我会对此一无所知？)。|2276688|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/pfxteam/|1|http://en.wikipedia.org/wiki/Queueing_theory^0|0|6|I|0|0|0|0|L|F|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

I'm doing something similar. I have messages coming in on MTA threads that need to be serviced on STA threads. 

I used a <a href="http://blogs.msdn.com/pfxteam/" rel="nofollow noreferrer">BlockingCollection</a> (part of the parallel fx extensions) that is monitored by several STA threads (configurable, but defaults to xr * the number of cores). Each thread tries to pop a message off the queue. They either time out and try again or successfully pop a message off and service it. 

I've got it wired with perfmon counters to keep track of idle time, job lengths, incoming messages, etc, which can be used to tweak the queue's settings. 

You'd have to implement a custom collection, or perhaps extend BC, to implement queue item priorities.

One of the reasons why I implemented it this way is that, as I understand it, <a href="http://en.wikipedia.org/wiki/Queueing_theory" rel="nofollow noreferrer">queueing theory</a> generally favors single-line, multiple-servers (why do I feel like I'm going to catch crap about that?).

blocks|key|366928|text|@grieve:网络是原生的，这意味着当在网络上使用缓冲区接收/发送数据时，它们被固定在内存中。请参阅我下面的评论进行详细说明。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366929|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

@grieve: Networking is native, meaning that when buffers are used the receive/send data on the network, they are pinned in memory. see my comments below for elaboration.

blocks|key|3321896|text|我知道这是一个古老的帖子，但我认为你应该看看ILNumerics项目中实现的内存池。我认为他们做的正是你需要的，这是一段非常好的代码。从http://ilnumerics.net/下载代码并查看文件ILMemoryPool.cs|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3321897|entityMap|0|LINK|mutability|MUTABLE|url|http://ilnumerics.net/^0|1W|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I know this is an old post, but I think you should take a look at the memory pool implemented in the ILNumerics project. I think they did exactly what you need and it is a very nice piece of code. 
Download the code at <a href="http://ilnumerics.net/" rel="nofollow">http://ilnumerics.net/</a> and take a look at the file ILMemoryPool.cs

We need to develop some kind of buffer management for an application we are developing using C#.

Essentially, the application receives messages from devices as and when they come in (there could be many in a short space of time). We need to queue them up in some kind of buffer pool so that we can process them in a managed fashion.

We were thinking of allocating a block of memory in 256 byte chunks (all messages are less than that) and then using buffer pool management to have a pool of available buffers that can be used for incoming messages and a pool of buffers ready to be processed.

So the flow would be "Get a buffer" (process it) "Release buffer" or "Leave it in the pool". We would also need to know when the buffer was filling up. 

Potentially, we would also need a way to "peek" into the buffers to see what the highest priority buffer in the pool is rather than always getting the next buffer.

Is there already support for this in .NET or is there some open source code that we could use?

Buffer pool management using C#

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们需要为使用C#开发的应用程序开发某种类型的缓冲区管理。本质上，应用程序在设备进入时接收消息(在短时间内可能会有许多消息)。我们需要在某种类型的缓冲池中对它们进行排队，这样我们才能以托管的方式处理它们。我们正在考虑以256字节为单位分配一个内存块(所有消息都小于这个大小)，然后使用缓冲池管理来拥有一个可用于传入消息的...

问使用C#进行缓冲池管理
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用C#进行缓冲池管理EN