Increase your file transfer speeds by up to 4x
supertcp.com
supertcp.com
Scrolling down to "How It Works", it doesn't really explain "how it works" but instead, it has vague phrases such as "better algorithms". If one then decides to click on more details via your blog post "Why the Internet is Slow" (which btw often returns "Resource Limit Is Reached"), it still doesn't explain the technical nitty gritty details.[1]
Those vague texts you've written may be ok for Wired Magazine or TechCrunch but for the HN crowd who is more sophisticated about hardcore technology, can you provide a more satisfying description of what it does? Is it jumbo packets? Changing ACKnowledgement timings? What exactly does it do that requires no new software to be installed?
[1]google cache in case the real pages are not responding:
"How it Works": http://webcache.googleusercontent.com/search?q=cache:Jb8UsXV...
"Why the Internet is Slow" http://webcache.googleusercontent.com/search?q=cache:HWoIkC7...
"Now, with a direct circuit between you and them the only limit on how quickly you could send data was how you encoded it and the speed of light (or, the speed of electricity anyway)....
"...And apparently somebody else thought of that which is why they built a protocol called the transport control protocol, or TCP...."
Thanks!
Is this TCP window scaling? Linux can already do this, not sure about Windows or Mac OS X, though I'd be surprised if they don't.
Is it larger initial window sizes (i.e. WSCALE with larger than normal buffers)? Again, Linux has this RFC implemented, and I'm pretty sure all the other major OSes do, as well. But, I guess this app could be increasing buffer sizes to allow WSCALE to negotiate larger windows.
I have a vague feeling this is snake oil. Possibly a GUI for adjusting some buffer sizes and enabling some options that aren't enabled, by default (because they can cause problems in some environments for some use cases).
If there were something other than hand-waving in the "how it works" and the "technical" blog posts, I might be less suspicious. But, there is nothing but unbacked assertions, seemingly random speed claims, and a pretty slick website.
I don't want to seem overly harsh here...I'm interested in what you're doing, if it is novel. But, extraordinary claims require extraordinary evidence, and you've made truly extraordinary claims. 4x speed up, without compression and without introducing new specifications that have to be implemented on both sides, would be absolutely revolutionary.
So, in the absence of evidence, I am inclined to call, "bullshit!".
I think what I've discovered is that the Hacker News community is more tech-savvy than originally thought. Sorry about that! Obviously we're missing some of the technical details of what we're trying to do. I'm going to work on a blog post to help clarify things, but for now you may be interested to know that SuperTCP is essentially a kernel-based TCP proxy. This allows us to–with only changes to one side of the connection–tweak every aspect of the data transmission as long as we stay within TCP's defined restrictions.
Yes, we tweak initial window sizes and lots of other things that can be easily changed on most operating systems, but our main differentiator is how we detect and utilize the available bandwidth, or really how we react to congestion when we see it. SuperTCP tries to be better than the other congestion control algorithms (CUBIC, Reno, NewReno, etc.) most operating systems support. That's where we're better.
Understatement of the year.
I am also worried about fairness: do SuperTCP streams muscle out other streams? Is that how they grab all the bandwidth?
TCP has back-off built-in for a reason: if everyone is as greedy as possible, massive congestion occurs.
Criticizing you from a pulpit is easy, kudos to you if you fix things up over time :-)
Ironic.
> or upload a YouTube video in 5 minutes instead of 50
I literally don't believe it. Even if you reduce it to pure UDP, you don't save that much from the TCP conversation
No! That's the beauty of it. SuperTCP is one of the only single-sided "better TCP" solutions out there. Put it on one side and you're ready to go.