Slow Ipod wifi on lan

gerdo

An average response time of 38ms is seriously slow in computing terms and any application will perform really poorly under those conditions.

Applications crossing a network will send millions of packets per second. If each one of those packets takes 38ms then that's quite a bottleneck

googler

gerdo wrote: »

Applications crossing a network will send millions of packets per second. If each one of those packets takes 38ms then that's quite a bottleneck

Do you see the app as described by the OP as generating 'millions of packets' .....?

gerdo

googler wrote: »

Do you see the app as described by the OP as generating 'millions of packets' .....?

Do you even know how a network works? The OP said it was a web app. Even the smallest web apps generate a lot of network traffic.

Maybe you should learn a bit about TCP/IP

prowla

gerdo wrote: »

Do you even know how a network works? The OP said it was a web app. Even the smallest web apps generate a lot of network traffic.

Maybe you should learn a bit about TCP/IP

You would expect the output of some tick boxes on a menu app to be really quite small...

googler

gerdo wrote: »

Do you even know how a network works? The OP said it was a web app. Even the smallest web apps generate a lot of network traffic.

Maybe you should learn a bit about TCP/IP

Maybe you could simply answer the question -

"Do you see the app as described by the OP as generating 'millions of packets' .....?"

moneyuser

prowla wrote: »

You would expect the output of some tick boxes on a menu app to be really quite small...

Not really sure what tick boxes has got to do with anything?

Anyway, has someone got some constructive advice on how to go about solving this problem? Further tests I should be performing to narrow down the problem?

googler

My take on it is that the ping time isn't the problem; however, another poster disagrees, and wonders if I know how a network works.

I freely confess that networks aren't my speciality, but I have worked on transactional processing in a mainframe context in the past.

As you've described it, the transaction, if I can call it that, between the iPod and the Processor doesn't appear to be that heavy in terms of data - waiter or waitress selects menu items, presses Enter, and these are transmitted to the Processor. No graphics, no reams of data, just a small selection of, as another poster puts it, 'tick boxes'.

If we're misunderstanding your app, please feel free to fill in more detail, but we're working with what you've told us.

Did you write the app, or was this done by a third party developer for you?

debitcardmayhem

gerdo wrote: »

An average response time of 38ms is seriously slow in computing terms and any application will perform really poorly under those conditions.

Applications crossing a network will send millions of packets per second. If each one of those packets takes 38ms then that's quite a bottleneck

Oh Dear, if only the app was capable of sending millions of packets per second and if it was only just pinging ie 32/64 bytes (depending on the implementation of ping) then that is 32 * 8 bits ie 256 bits millions of times a second then I would guess then the OP would need several Gb cards to handle just that (forget the wireless bit) each packet has a 20 byte header let alone any payload.

gerdo wrote: »

Do you even know how a network works? The OP said it was a web app. Even the smallest web apps generate a lot of network traffic.

Maybe you should learn a bit about TCP/IP

Ooops shoots self in foot , perhaps you should learn a bit about TCP/IP and maybe maths too

debitcardmayhem

moneyuser wrote: »

Not really sure what tick boxes has got to do with anything?

Anyway, has someone got some constructive advice on how to go about solving this problem? Further tests I should be performing to narrow down the problem?

try explaining exactly what your problem is , and if your iPods are working only on 802.11b I would try setting the router to only use 'b'

GunJack

^^^ that's the most constructive comment so far....any router having to work a mixed protocol will not perform optimally, and in some cases can even lead to devices on one of the protocols not being serviced properly and can cause poor responses and even dropouts. Practical example:- xbox on 11g, laptop on 11b, when the laptop wifi was in use it caused the xbox wifi to lag, drop connection, etc....changed laptop for 11g, locked router to 11g, no probs for xbox when new laptop in use