Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

It's Always TCP_NODELAY

brooker.co.za

Post reply on HN
Print view View original

181–186 of 186 posts

Re: It's Always TCP_NODELAY

#181

Post by switchbak »

nomel wrote: post #165
switchbak wrote: post #45

Earlier quoted context omitted.

My understanding is that no one used hubs anymore, so your collision domain goes from a number of machines on a hub to a dedicated channel between the switch and the machine. There obviously won’t be collisions if you’re the only one talking and you’re able to do full duplex communications without issue.

> My understanding is that no one used hubs anymore this is absolutely hilarious.

Your comment is absolutely devoid of content.

Admittedly, I’m no networking expert but it was my understanding that most installs now use switches almost exclusively. Are you suggesting otherwise?

A quick search would seem to indicate I’m right. Do you mind elaborating on your snark?

Re: It's Always TCP_NODELAY

#182

Post by [deleted] »

immibis wrote: post #180
mort96 wrote: post #176

Earlier quoted context omitted.

> That's not just busywork - it's also an abstraction violation. You used AI to write this didn't you? Your sentence structure is not just tedious - it's a dead give-away.

No, I did not. Am I now forbidden from using sentence structures that AI has also used? That's not just stupid - it's insane. You know that's not even an em-dash, right?

[deleted]

Re: It's Always TCP_NODELAY

#183

Post by CamperBob2 »

littlecranky67 wrote: post #178
CamperBob2 wrote: post #156

Earlier quoted context omitted.

Maybe, maybe not, whatever. I was testing some low-bandwidth voice chat code using two unloaded PCs sitting on the same desk. I nearly jumped out of my skin when "HELLO, HELLO?" came through a few seconds late, at high volume, after I had already concluded it wasn't working. After ruling out latency on the audio side, TCP_NODELAY solved the problem. All respect to Animats, but whoever thought this should be the defau…

Whatever your issue in that setup was, NODELAY had nothing to do with it

Then why did it stop happening when NODELAY was used?

Re: It's Always TCP_NODELAY

#184

Post by littlecranky67 »

CamperBob2 wrote: post #183
littlecranky67 wrote: post #178

Earlier quoted context omitted.

Whatever your issue in that setup was, NODELAY had nothing to do with it

Then why did it stop happening when NODELAY was used?

Hard to say without looking at the complete setup - and probably just a side-effect of the underlying issue. The question is, why did you have such high RTTs? That already points to a different cause.

I would even argue that NODELAY for a VoIP solution makes no sense - why are you even using TCP instead of UDP in the first place?

Re: It's Always TCP_NODELAY

#185

Post by nomel »

switchbak wrote: post #181
nomel wrote: post #165

Earlier quoted context omitted.

> My understanding is that no one used hubs anymore this is absolutely hilarious.

Your comment is absolutely devoid of content. Admittedly, I’m no networking expert but it was my understanding that most installs now use switches almost exclusively. Are you suggesting otherwise? A quick search would seem to indicate I’m right. Do you mind elaborating on your snark?

"No one" and "no new installations" are not the same. There are many many many millions of hubs out there in the world. The statement, as written, is just ludicrously naive, entirely disconnected from reality.

Re: It's Always TCP_NODELAY

#186

Post by switchbak »

nomel wrote: post #185
switchbak wrote: post #181

Earlier quoted context omitted.

Your comment is absolutely devoid of content. Admittedly, I’m no networking expert but it was my understanding that most installs now use switches almost exclusively. Are you suggesting otherwise? A quick search would seem to indicate I’m right. Do you mind elaborating on your snark?

"No one" and "no new installations" are not the same. There are many many many millions of hubs out there in the world. The statement, as written, is just ludicrously naive, entirely disconnected from reality.

JFC man, you need to get outside more. Wow.
Post reply on HN