Help fix performance problems in VS
-
This sounds like an interesting VS plugin: VS PerfWatson[^]. The plugin detects when Visual Studio hangs. When it hangs, it sends the hung stack trace to MS. MS spends less time investigating VS performance problems and more time fixing them[^]. :cool:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
When it hangs, it sends the hung stack trace to MS. MS spends less time investigating VS performance problems and more time fixing ignoring them
You spelled a word wrong. Don't worry, I fixed it...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
This community is so damn cynical! ;P
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoActually, we're realists...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
This sounds like an interesting VS plugin: VS PerfWatson[^]. The plugin detects when Visual Studio hangs. When it hangs, it sends the hung stack trace to MS. MS spends less time investigating VS performance problems and more time fixing them[^]. :cool:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoFrom the link: If VS goes unresponsive for more than 2 seconds, Perf Watson grabs a stack frame. That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds, it just feels sluggish. Usability tests have proven over and over that if something takes more than 100 ms, users notice it's not instantaneous. By 300 ms, it becomes obvious. By 1 second it becomes measurably disruptive. Microsoft has an excellent usability department, so why do so many divisions and teams at Microsoft ignore them? (Rhetorical question--solving customer problems takes a back seat to using the latest "in" technology.)
-
From the link: If VS goes unresponsive for more than 2 seconds, Perf Watson grabs a stack frame. That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds, it just feels sluggish. Usability tests have proven over and over that if something takes more than 100 ms, users notice it's not instantaneous. By 300 ms, it becomes obvious. By 1 second it becomes measurably disruptive. Microsoft has an excellent usability department, so why do so many divisions and teams at Microsoft ignore them? (Rhetorical question--solving customer problems takes a back seat to using the latest "in" technology.)
Yep, there are sluggish parts. Still, I'm happy if they fix some of the hangs. Step in the right direction.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
From the link: If VS goes unresponsive for more than 2 seconds, Perf Watson grabs a stack frame. That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds, it just feels sluggish. Usability tests have proven over and over that if something takes more than 100 ms, users notice it's not instantaneous. By 300 ms, it becomes obvious. By 1 second it becomes measurably disruptive. Microsoft has an excellent usability department, so why do so many divisions and teams at Microsoft ignore them? (Rhetorical question--solving customer problems takes a back seat to using the latest "in" technology.)
Have you noticed the scrolling lag? In a long file, scrolling lags for about a 1/4 second and then picks up again every second or two.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Actually, we're realists...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Actually, I think too many people here are crotchety, sarcastic whiners who complain about everything, do little or nothing to improve things, and couldn't do a better job themselves building said [product/tech] if they tried. Still, that doesn't stop them from whining.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Actually, I think too many people here are crotchety, sarcastic whiners who complain about everything, do little or nothing to improve things, and couldn't do a better job themselves building said [product/tech] if they tried. Still, that doesn't stop them from whining.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoHow do you expect us to act when after reporting bugs to Microsoft, we're told they're not going to fix the problem. That's happened to me twice - once with the syntax highlighting issues in VS2010, and another time regarding non-client-hit testing for a windows bug that they freely admitted was an actual bug. Whinging? Nope - I think it's more like spitting into the wind.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Have you noticed the scrolling lag? In a long file, scrolling lags for about a 1/4 second and then picks up again every second or two.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I noticed so much lag everywhere that I finally just uninstalled it and continued with VS 2008.
-
How do you expect us to act when after reporting bugs to Microsoft, we're told they're not going to fix the problem. That's happened to me twice - once with the syntax highlighting issues in VS2010, and another time regarding non-client-hit testing for a windows bug that they freely admitted was an actual bug. Whinging? Nope - I think it's more like spitting into the wind.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Yep, happened to me several times. In fact, there's one case on MS Connect that I filed in 2002, and they still haven't resolved it. (keeps getting, "considered for a future version"). It sucks. IT's like I tell my kids. Complain about it once, OK. Complain about it for weeks on end, not OK. Sometimes things can't be fixed. Sad fact of life. Get over it. Move on. Stop complaining.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
I noticed so much lag everywhere that I finally just uninstalled it and continued with VS 2008.
Funny, because VS 2008 had a HUGE problem with big files. Scrolling would come to a halt. Improvements were made in VS 2010[^]. I think if God gave you all an IDE, you'd find something to bitch about it and yearn for "the good ol' days" of Windows 3.1 Edit.exe :thumbsdown:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
How do you expect us to act when after reporting bugs to Microsoft, we're told they're not going to fix the problem. That's happened to me twice - once with the syntax highlighting issues in VS2010, and another time regarding non-client-hit testing for a windows bug that they freely admitted was an actual bug. Whinging? Nope - I think it's more like spitting into the wind.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
How do you expect us to act
Try to improve the situation. This thread is about a VS plugin that can improve the situation. Instead of bitching, and joking about all the places MS sucks, do something about it. This VS plugin is a small step in the right direction. Install it. Let it send hangs to MS. VS improves, and there's just a little less bitching to be done in the world. Win.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
John Simmons / outlaw programmer wrote:
How do you expect us to act
Try to improve the situation. This thread is about a VS plugin that can improve the situation. Instead of bitching, and joking about all the places MS sucks, do something about it. This VS plugin is a small step in the right direction. Install it. Let it send hangs to MS. VS improves, and there's just a little less bitching to be done in the world. Win.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
Let it send hangs to MS. VS improves
I think you're assuming a bit too much, there.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Funny, because VS 2008 had a HUGE problem with big files. Scrolling would come to a halt. Improvements were made in VS 2010[^]. I think if God gave you all an IDE, you'd find something to bitch about it and yearn for "the good ol' days" of Windows 3.1 Edit.exe :thumbsdown:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoGod doesn't exist, so we shouldn't expect anything from him any time soon. Edlin has a subtle syntax highlighting bug in it. Epic fail.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Funny, because VS 2008 had a HUGE problem with big files. Scrolling would come to a halt. Improvements were made in VS 2010[^]. I think if God gave you all an IDE, you'd find something to bitch about it and yearn for "the good ol' days" of Windows 3.1 Edit.exe :thumbsdown:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoI don't edit huge files. Lots of very small ones. That's what makes VS 2010 so pathetic. The article claims VS 2010 text editor is "blazing fast." It isn't. It's barely slow enough that it gives you a nagging feeling that it just isn't right. Now that I think about it, it reminds me of Word for DOS.
Judah Himango wrote:
I think if God gave you all an IDE, you'd find something to bitch about it and yearn for "the good ol' days" of Windows 3.1 Edit.exe :thumbsdown:
I hate this bullshit response. When I pay $800+ for a product, I expect it to be damn good, not barely acceptable for the free version. I would be deeply embarassed to ship, let alone sell, a product this flawed. That tells you everyhing you need to know about the mindset of the developer tools management at Microsoft.
-
From the link: If VS goes unresponsive for more than 2 seconds, Perf Watson grabs a stack frame. That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds, it just feels sluggish. Usability tests have proven over and over that if something takes more than 100 ms, users notice it's not instantaneous. By 300 ms, it becomes obvious. By 1 second it becomes measurably disruptive. Microsoft has an excellent usability department, so why do so many divisions and teams at Microsoft ignore them? (Rhetorical question--solving customer problems takes a back seat to using the latest "in" technology.)
Joe Woodbury wrote:
That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds
Really? Mine freezes all the time... I could be in the middle of typing, and it'll just suddenly lock up for a good minute or two. It's gotten to the point that when it happens, I just browse a few websites and check back now and then to see if it's woken up yet.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
Joe Woodbury wrote:
That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds
Really? Mine freezes all the time... I could be in the middle of typing, and it'll just suddenly lock up for a good minute or two. It's gotten to the point that when it happens, I just browse a few websites and check back now and then to see if it's woken up yet.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)I haven't used it enough to find out. I got fed up with it before I got to that point.
-
Judah Himango wrote:
Let it send hangs to MS. VS improves
I think you're assuming a bit too much, there.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 19973 possible outcomes of trying to improve the situation: -Best case: Microsoft fixes many hangs. VS improves. -Likely case: Microsoft fixes a few common hangs. VS improves. -Worst case: Microsoft fixes no hangs. VS doesn't improve. Even for the worst case, it's still as good as your current solution, which is bitching about it and nothing getting fixed. Try to improve the situation. Install the damn plugin. There will be at least one less bitchfest in the years to come.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
3 possible outcomes of trying to improve the situation: -Best case: Microsoft fixes many hangs. VS improves. -Likely case: Microsoft fixes a few common hangs. VS improves. -Worst case: Microsoft fixes no hangs. VS doesn't improve. Even for the worst case, it's still as good as your current solution, which is bitching about it and nothing getting fixed. Try to improve the situation. Install the damn plugin. There will be at least one less bitchfest in the years to come.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
Install the damn plugin
Why should I? Microsoft has a pretty poor track record as far as I'm concerned. If I'm gonna get dirty, I insist that Microsoft get in the mud pit with me. they've shown no desire to do that. I kind of enjoy this love/hate thing we have going here. You love VS2010, we hate it. It's our own version of yin/yang, providing balance in the universe.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Yep, there are sluggish parts. Still, I'm happy if they fix some of the hangs. Step in the right direction.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
Yep, there are sluggish parts.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I don't edit huge files. Lots of very small ones. That's what makes VS 2010 so pathetic. The article claims VS 2010 text editor is "blazing fast." It isn't. It's barely slow enough that it gives you a nagging feeling that it just isn't right. Now that I think about it, it reminds me of Word for DOS.
Judah Himango wrote:
I think if God gave you all an IDE, you'd find something to bitch about it and yearn for "the good ol' days" of Windows 3.1 Edit.exe :thumbsdown:
I hate this bullshit response. When I pay $800+ for a product, I expect it to be damn good, not barely acceptable for the free version. I would be deeply embarassed to ship, let alone sell, a product this flawed. That tells you everyhing you need to know about the mindset of the developer tools management at Microsoft.
Joe Woodbury wrote:
I hate this bullsh*t response.
You should, it hits the mark. I've been in the CP community for over a decade. In the last 3 years, it's become fashionable to complain, whine, and make sarcastic remarks about *everything*. This whole thread is a case in point. You incessantly complain about VS, yet when Microsoft tries to improve it by learning more about performance issues, you complain about *that*. You complain about the paid version, you complain about the free version. You talk as if you could write software that is better. If that's the case, show me your work. I'll delight in finding things to complain about. This community has devolved into a group of old sarcastic, jaded, cynical, whiny nerds. All I see is bitching, never any attempts to improve the situation. Makes me want to find another place to talk nerd stuff with other devs. Didn't used to be like this.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango
