I have had for a while a problem with my upload speed with my AT&T DSL. I have been a happy customer with SBC for 5 years now and wasn’t about to just change. I also have DirectTV instead of cable and I’m very content with DirectTV.
My upload speeds for the last 4 months have been shaky and very frustrating. I was testing it often with speakeasy.com and I knew that the upload was slow and that reported it around 50-70 kpbs on average. Sometimes it got up to 200 kbps upload speed but I knew that something was wrong. I have the Pro package at $30 from AT&T which guarantees around 3 mb download and 512 upload speeds. I’ve been pretty busy working so never really did anything about it. Tonight I finally looked into it after several support tickets and I believe I solved the problem. First, let me say that I “think” it’s solved. We will see over the course of the next week(s) if this remains the case.
What I found out was that I recently upgraded my entire PC. Well I guess rebuilt it really. I installed a nice new shiny ASUS P5E motherboard about 4 months ago and I’ve been running Vista 64-bit. Ever since then I didn’t really think to link anything with ASUS but I think I ended up linking it to its
Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller card. ASUS boards are so good, I don’t usually second guess it. But I believe the problem ended up being that in the Ethernet device properties, by default the Speed & Duplex was set to “Auto-Negotiation”:
I changed it to 10 Mbps Full Duplex and I swear that both upload and download speeds have improved a ton:
I now get a solid 2.5 mb on average download (whereas before it ranged and changed intermittently between 1.5 – 2.5 Mbps download and was again around only 70 mbps upload).
I hope this helps someone who has had the same issues with either download or upload speeds. Check your Ethernet card, you’d be surprised.
Please kick/dzone/digg if this post if it was helpful.
SharePoint SharePoint how sad are we
Your marketing promise me everything under the sun & as far as my eyes can see
A hidden cost, a nasty toss, a huge 5 year loss
Go hire a whole team, 3rd party pugs-ins, SharePoint consultants with nothing BUT cost
SharePoint SharePoint, I hate you so
You’re a clown with a funky smile, but do you fool me? hell no
You are a big smelly beast running sweaty into the night
Because your API is so bad, developers constantly put up a fight
SharePoint SharePoint what horrible code
Code that must dance around this API that’s just too messy and cold
I love to become a master of all trades
How to debug SharePoint’s bad errors, pile of code, and adding never-ending band-aids
SharePoint SharePoint, you’re a big ass joke
You’re page model not even in .NET 3.5 yet, sad, so you leave me in smoke
When the next upgrade comes, developers better run for the hills
And hope you never customized it in the past, else late nights, & footin the bills
I leave you with this video, and last comments at the end.
I would much rather know I can code and extend my application with quality design patterns and take just a little more time with it without boundary for the business, rather than become a master of disaster at getting around a lousy SharePoint bloated API and funky way to code around it and hack the thing or deal with its lousy limitations. Instead of developing, you end up throwing a ton of plugins or worse, deciding to use a system like K2 or InfoPath (a huge messy beasts) just to do workflow instead of using straight code & WWF in the first place.
Ok out of box, but not ok to extend my friend. Because in the end, cost beats custom on this one (if you are thinking about an end-all solution other than just document management that is). leave Sharepoint to the out-of-box document management. Leave the rest of the business to REAL code. Don’t try to squeeze something that it is not.
Just a sample of a few of probably hundreds of related links on the web:
Sharepoint is not a good development platform (by Jeffery Palmero)
SharePoint 2007: Pointedly unskinnable
Is creating a view on SharePoint tables bad style?
I'm a developer, and I hate SharePoint
Sharepoint 2007 - insanely bad HTML
SharePoint Development is an Adventure!
I hate SharePoint (and so do you) – Part 1
I hate SharePoint (and so do you) – Part 2
SharePoint Sucks.
Why SharePoint Portal Server is Terrible
SharePoint sucks at document management - or does it? A metal perspective
"Developing for sharepoint is nothing but a nightmare. The system is overly complex, unintuitive and just plain bizarre"
Bad naming - Sharepoint Features
The Good, The Bad and The Ugly of Sharepoint 2007 Development
What’s my point? Yes, this is a rant, because I can. It’s a horrible development platform, inflexible, and a huge cost to organizations that ever want to “extend” this pile all due to Microsoft’s over marketing of a glamorous UI that is fine if you DON’T try to customize it or extend it beyond it’s out-of-box functions. Sure, you can extend…and break your organization’s back and piss off your developers who hate working in it…at least those developers who have worked with good code / design patterns, etc. I don’t claim to know anything about it… because I’ve purposely stayed away from it my entire career because I have seen what problems and code this thing requires you to manage and put out in past jobs that used it, including 2007/MOSS.
Oh, and try to unit test SharePoint with proper Unit Testing without having to install the damn server and ways to test it. Have fun with that.
So what’s the problem? Why is it so hard to unit test SharePoint applications?
"This is the kind of stuff that really makes unit testing a turn off for me"
Looks like a bunch of "FUN FUN" weird ass code just to Unit Test. Oh SharePoint
Fun, Fun, and more Fun
Enough said, and this is my opinion and I’ve seen environments use this pile for enterprise based applications internally and externally and it was just a huge boiling pot mess of code, errors, and just weirdness to support this beast.
Bye the way on the right nav, there is a SharePoint Poll. Please take it.
Cheers & God Bless to JQuery, Design Patterns, ASP.NET 3.5 MVC, good ORM, Code that is Unit Testable (without barriers), and the rest. Down with SharePoint as an “end-all” solution.
