Because RubyForge is pushing A LOT of bandwidth, we transitioned to a faster
ADSL line (was 1.5/384 now 6.0/768) but are experiencing some crappy
performance (for CVS commits, etc).
Thats interesting, I have had a similar thing happen from going from a 512:256 adsl line to 1024:256. Basically short burst transmissions are really quite slow (anything really sub 32k), such that sshing into my machine or using my webmail is slower now that it was before. I tried discussing it with my ISP but got nowhere with them. I hope whatever they are changing for you works.
Rob
Hm...well, we are getting kick-butt performance this morning! Maybe my
swift kick of my ISP did the trick 
Can folks let me know what they
think of the current response?
Best,
-rich
···
On 8/6/04 4:50 AM, "Robert McGovern" <robertm@spellmanhv.co.uk> wrote:
Because RubyForge is pushing A LOT of bandwidth, we transitioned to a faster
ADSL line (was 1.5/384 now 6.0/768) but are experiencing some crappy
performance (for CVS commits, etc).
Thats interesting, I have had a similar thing happen from going from a 512:256
adsl line to 1024:256. Basically short burst transmissions are really quite
slow (anything really sub 32k), such that sshing into my machine or using my
webmail is slower now that it was before. I tried discussing it with my ISP
but got nowhere with them. I hope whatever they are changing for you works.
Rob
Could that be the Nagle algorithm kicking in?
Cheers
Dave
···
On Aug 6, 2004, at 4:50, Robert McGovern wrote:
Thats interesting, I have had a similar thing happen from going from a 512:256 adsl line to 1024:256. Basically short burst transmissions are really quite slow (anything really sub 32k), such that sshing into my machine or using my webmail is slower now that it was before. I tried discussing it with my ISP but got nowhere with them. I hope whatever they are changing for you works.
I'd say that it fills the shoes of 'kick-butt' quite nicely!!
-Rich
···
On Fri, 6 Aug 2004 21:44:18 +0900, Richard Kilmer <rich@infoether.com> wrote:
Hm...well, we are getting kick-butt performance this morning! Maybe my
swift kick of my ISP did the trick Can folks let me know what they
think of the current response?
Best,
-rich
On 8/6/04 4:50 AM, "Robert McGovern" <robertm@spellmanhv.co.uk> wrote:
>> Because RubyForge is pushing A LOT of bandwidth, we transitioned to a faster
>> ADSL line (was 1.5/384 now 6.0/768) but are experiencing some crappy
>> performance (for CVS commits, etc).
>
> Thats interesting, I have had a similar thing happen from going from a 512:256
> adsl line to 1024:256. Basically short burst transmissions are really quite
> slow (anything really sub 32k), such that sshing into my machine or using my
> webmail is slower now that it was before. I tried discussing it with my ISP
> but got nowhere with them. I hope whatever they are changing for you works.
>
> Rob
>
>
>
>
Dave Thomas wrote:
Thats interesting, I have had a similar thing happen from going from a 512:256 adsl line to 1024:256. Basically short burst transmissions are really quite slow (anything really sub 32k), such that sshing into my machine or using my webmail is slower now that it was before. I tried discussing it with my ISP but got nowhere with them. I hope whatever they are changing for you works.
Could that be the Nagle algorithm kicking in?
Nagle is a property of the TCP stack, not the network connection. Changing your ISP shouldn't affect that.
I'd take a look at the round-trip times. Long RTTs kill interactive things like SSH but don't have much effect on bulk transfers as long as there's enough TCP window to keep the pipe full.
Steve
···
On Aug 6, 2004, at 4:50, Robert McGovern wrote: