Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
Leaving Some Headroom
Leaving Some Headroom
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, July 26, 2012 12:40 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 3:19 PM
Points: 31,526,
Visits: 13,863
Comments posted to this topic are about the item
Leaving Some Headroom
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1335580
TravisDBA
TravisDBA
Posted Thursday, July 26, 2012 7:37 AM
Ten Centuries
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 10:46 AM
Points: 1,290,
Visits: 3,001
"I'm not sure how I'd want this to work on my SQL Servers. After all, any load I placed on them wouldn't necessarily just occupy CPU. It would also impact the buffer pool, as the type of process I chose would influence what would stay (or go) in that bit of memory."
You can throttle and control individual processes (CPU & Memory) in SQL Server now. It's called the Resource Governor.
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...
"
Post #1335841
Michael Valentine Jones
Michael Valentine Jones
Posted Thursday, July 26, 2012 8:32 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 2:14 PM
Points: 2,969,
Visits: 10,615
Putting an artificial and unneeded CPU load on a server, putting large files that are not needed on the disk, and generating unneeded disk or network IO seem like things that could cause as many problems as they fix.
Post #1335887
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, July 26, 2012 11:27 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 3:19 PM
Points: 31,526,
Visits: 13,863
TravisDBA (7/26/2012)
"I'm not sure how I'd want this to work on my SQL Servers. After all, any load I placed on them wouldn't necessarily just occupy CPU. It would also impact the buffer pool, as the type of process I chose would influence what would stay (or go) in that bit of memory."
You can throttle and control individual processes (CPU & Memory) in SQL Server now. It's called the Resource Governor.
Resource governor doesn't limit CPU and memory for individual processes. It works with groups of logins, and it doesn't provide any ability to prevent resources from being used without a competing group.
So if your web site uses a common login, or all logins from your website, then you do not limit resources between these processes. If one pegs the server, they all suffer. They are all in the same pool.
Potentially you could use a second workload group to stick an artificial load on the server and remove it when you needed more resources.
The memory limits are not for the buffer pool, but query memory. Important, but not the same thing.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1336010
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, July 26, 2012 11:28 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 3:19 PM
Points: 31,526,
Visits: 13,863
Michael Valentine Jones (7/26/2012)
Putting an artificial and unneeded CPU load on a server, putting large files that are not needed on the disk, and generating unneeded disk or network IO seem like things that could cause as many problems as they fix.
They can. Or they can save you in a crisis, especially disk issues. As with most things, it depends.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1336012
GSquared
GSquared
Posted Thursday, July 26, 2012 12:15 PM
SSCoach
Group: General Forum Members
Last Login: 2 days ago @ 1:45 PM
Points: 15,442,
Visits: 9,572
It makes sense in the same way a reserve tank made sense on old VWs. Sure, you could consolidate it all into one fuel tank and get the same total capacity, but having it separate and only accessible if you flipped a switch or whatever, saves you from "oops, I wasn't watching the fuel gauge and now I'm totally out" situations.
And with modern servers able to go from "c'mon, gimme something to do" to "he's dead now!" pretty fast under the right (wrong) circumstances), you don't have to take your eye off that "fuel gauge" very long for it to count as "not watching it".
So, yeah, I can see the value to this kind of thing. Would definitely have to be documented and drilled as part of your DR/BC plan, or it wouldn't be any use. (Walk five miles to the nearest gas station, buy and fill a gas can, get someone there to give you a ride back to the car, only to be told by that person, "you do know your car has an emergency reserve tank, right?")
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1336043
benjamin.reyes
benjamin.reyes
Posted Thursday, July 26, 2012 1:56 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Friday, May 31, 2013 9:48 AM
Points: 198,
Visits: 746
I presented this idea to my SAN admin. I don't think he's was very enthusiastic about the idea.
(ノ °益°) 彡┻━┻
Post #1336105
TravisDBA
TravisDBA
Posted Friday, July 27, 2012 7:49 AM
Ten Centuries
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 10:46 AM
Points: 1,290,
Visits: 3,001
The memory limits are not for the buffer pool, but query memory. Important, but not the same thing.
Good point Steve , it is query memory, and they are not the same thing. i stand corrected.
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...
"
Post #1336513
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.