limitations of meteor

[Dave Dev]

Good Morning,

I'm looking to use deacon / meteor as a secondary push
notification solution for an android application, and I'm trying to
figure out if meteor will handle my requirements. The application
will require a huge number of concurrent connections/channels (50K or
more), with messages being sent only occasionally (a couple times an
hour). I read in previous posts that meteor does not scale
particularly well in that scenario, and I will most likely implement
my own scaling solution... I'll just start a bunch of meteor servers
and try to spread the urls evenly among the clients.

I was wondering what the expected limitations of meteor were in this
case:

1.) How many concurrent connections and channels is a single meteor
server expected to handle? Are there software cutoffs that might drop
connections?

2.) Deacon only uses the longpoll option and I'm trying to figure out
if it's worth developing a custom client library. Would a different
connection type be better for my scenario?

Thanks!

-Dave