Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

sql server memory Expand / Collapse
Author
Message
Posted Wednesday, January 9, 2013 11:08 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Monday, November 17, 2014 12:50 PM
Points: 13,872, Visits: 9,598
Oracle_91 (1/8/2013)
Hi Gus,

I am just testing/learning memory concepts over here. not to throttle any productions systems


Ah! That makes sense then.

Yeah, learning how to deliberately overload the data cache vs the plan cache vs crushing the O/S space, etc., are all useful things. Good idea. Gives you a better idea of what can do those kinds of things, so you can fix it when it happens in the wild.

Try some things like loading too many big tables into active queries, all at the same time.

Try firing off a bunch of hyper-complex queries all at once.

Try non-deadlock long locks.


- 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 #1404906
Posted Wednesday, January 9, 2013 6:40 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:30 PM
Points: 3,204, Visits: 6,067
You may also try to run a query with a huge IN clause....


Post #1405109
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse