Apple 推送通知服务服务器负载?

发布于 2024-08-06 05:26:36 字数 140 浏览 3 评论 0原文

我正准备建立一个 APNS 消息服务器,我想知道是否有人对 APNS 服务器负载进行过任何分析,他们可以分享。最低服务器规格、每秒最大消息数等等。

谢谢!

编辑:我计划使用 .NET 来实现这一点,但是有关任何平台的信息都将非常有用。

I'm preparing to set up a APNS message server, and I was wondering if anybody has done any analysis on APNS server load that they would be able to share. Minimum server specs, maximum messages per second, anything like that.

Thanks!

edit: I'm planning to implement this with .NET, but info about any platform would be incredibly useful.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

心是晴朗的。 2024-08-13 05:26:37

对于我的应用程序(大约有 24,000 次下载),我发现平均每天发送大约 1300 条消息。

这些数字很低,但我的客户群也没有那么大。但我想我不妨贡献一些信息。 :-)

我的通知提供程序大部分时间都处于空闲状态,因此如果我需要的话,可以使用更多的容量。

此时它也使用很少的内存(大约 13 MB - 我用 Python 实现了我的提供程序,并且怀疑其中大部分被运行时占用)。

我正在 Media Temple dv(特别是基本配置)上运行。

我还没有推断出这些数字来找出我的理论最大值,但由于我的应用程序的利基市场,目前这并不让我担心。我有很多可以扩展的能力。

希望能有所帮助。

克里斯。

For my application (which has about 24,000 downloads) I am seeing an average of of about 1300 messages sent a day.

Those are low numbers, but then my client base isn't that large either. But I figure I might as well contribute some info. :-)

My notification provider is idle most of the time so there is MUCH more capacity available if I need it.

Its also using very little ram at this point (somewhere around 13 mb - I implemented my provider in Python and suspect most of that is taken up by the run time).

I am running on a Media Temple dv (specifically the Base configuration).

I haven't extrapolated out the numbers to find what my theoretical maximum would be, but because of the niche market of my application its not something that worries me at this point. I have lots of capacity to scale with.

Hope that helps a bit.

chris.

夏天碎花小短裙 2024-08-13 05:26:37

一位 Apple 开发人员提到,100,000 条消息并不算大,这并不能真正回答您的问题,但我不认为发送实际消息会成为瓶颈。
任何可以处理数据库工作的服务器都应该可以很好地发送消息。该协议有意做到轻量级。

One of the Apple devs mentioned that 100,000 messages is not considered a large amount, that doesn't really answer your question, but I wouldn't expect that sending the actual messages would be the bottleneck.
Any server that can handle your database work should be fine for sending the messages out. The protocol is intentionally light-weight.

染年凉城似染瑾 2024-08-13 05:26:37

每秒没有最大消息数。

There are no maximum messages per second.

挖个坑埋了你 2024-08-13 05:26:37

您应该考虑到每条消息必须小于 256 字节。否则 Apple 将拒绝您的消息。您还可以查看 MonoPush。据我所知,他们正在 .Net 框架之上构建他们的产品。

You should consider that every message must be smaller than 256 Byte. Otherwise Apple will be reject your messages. And you can also check MonoPush. AFAIK they are building their products top of the .Net Framework.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文