Am 16.07.2009 um 15:19 schrieb Richard Dobson:
Just because a connection isn't being used 100% doesnt mean you wont have problems all sorts of networking issues come into play, i.e. the amount of connections you are opening in quick succession (some OS's, routers and ISPs have rate limits),
NetBSD is known to handle thousands of connections without any performance impact. The machine _IS_ the router and the ISP does not have any limits at all - in fact, this ISP even allows running servers and P2P, explicitly.
are you running any P2P clients over the same connection? (these can cause problems because of the sheer amount of connections they open)
No.
just the asynchronous nature of ADSL on its own can cause issues
Then the upstream would be used 100%, but the downstream be mostly idle. But this is not the case.
ADSL can have serious contention issues especially if you are using one of the cheapo home accounts (i.e. in the UK that would be people like TalkTalk and Tiscali).
Not the case here.
Have you tried running the server from an alternate location? so you can be sure its not your connection, that would be the first thing I would try when faced with your setup.
The connection definitely isn't the problem, as it's mostly idle and with low pings during login. If there's a hardware limitation, it might be the CPU.
Well it does sound like either a connection/bandwidth issue or a bug in ejabberd then, just because other people are having the same issue doesn't necessarily mean it isn't something to do with your setup, rather than protocol.
Well, it might be fixable by using another implementation, but it would also be possible to have a protocol that wouldn't even allow these flaws.
-- Jonathan
PGP.sig
Description: Signierter Teil der Nachricht
