Helpful ReplyCore Parking

I know I've seen talk of this before, and I'm wondering how and if core parking effects my laptop performance. It presently appears to be enabled as I've been watching the CPU resource monitor to evaluate my current situation to decide if I need to get a new system or can tweak this one better, somehow, to maximize performance[some of that already having been done].

I found an older post on this very topic:  http://forum.cakewalk.com/tm.aspx?m=1861804

Anybody here with an i7 laptop using core parking turned off? It appears to be for better battery management, but does it also cause temperature changes and overheating perhaps?

Here is a simple but effective method for enabling all cores at all times: http://engrjpo.wordpress.com/2011/05/08/disable-cpu-core-parking/

The question remains as to how much, or if disabling core parking is beneficial with a laptop that isn't running on battery power. I'm trying to get some definitive answers from DAW power users.

do not do it period.. its old and pointless now especially on a laptop
turn off the acpi battery...

Kreative


The question remains as to how much, or if disabling core parking is beneficial with a laptop that isn't running on battery power. I'm trying to get some definitive answers from DAW power users.

I tested all this kind of tweaking when there was some heated debate going round whether it was worthwhile on older i7 chips.  I don't know even if there was any benefit there  but since I've been running a 2nd Generation i7 Sandy bridge chip I concluded there is nothing to be gained except higher temperatures and brain ache.

I run with a 64 samples buffer all day long without pops or glitches and power to burn so I figured why bother.  All my system power settings are the BIOS (optimised/turbo) defaults with only slight tweaks to the Windows High Performance power settings to prevent stuff like USB from auto-sleeping.

Thanks for your input. it was a heated debate that seemed to go 'round in circles. I found that I eliminated some of my audio and resource headaches by reducing some background tasks that were giving me intermittent glitches. I might benefit from a second or third gen chipset, but for now have what I have to work with.

Two issues: rise time, thread allocation

Most users will never notice the need for these two issues to be addressed. Except when they interfere with a specific demanding task.

Because of the speed of current computers users are usually not aware of all the auto updates, and little wait times. Consequently the comments about doing no tweaking with w7.

But, I surmise those who do no tweaking are also the ones who experience drop-outs, stutters, clicks,... Especially when working with large projects.

And they then complain that Sonar,...  is to blame when really it is the auto-defrag , updates for windows, adobe, java, AV,.... that they refuse to disable.

I am an old dude. My approach is to wring every last bit of performance from the box before I replace any componant.

And I do not want the defragger starting and interferring with my happiness.

So we have a consensus on core parking. Not a problem.

Is there agreement on disabling TurboBoost?

jcschild


do not do it period.. its old and pointless now especially on a laptop
turn off the acpi battery...

Why do you say we shouldn't turn off the core parking on desktop workstations?
 

slartabartfast


So we have a consensus on core parking. Not a problem.

Is there agreement on disabling TurboBoost?

I'm not sure either.

I use an H67 board so I have no means of over clocking so I'm basically running happily at stock speeds and there is therefore some benefit in performance to be had in having it enabled.

Whether that is the case if you are over clocking I am unable to test or ascertain.  So I'd suspect it would be dependant on your setup to some degree.

Freddie H

jcschild


do not do it period.. its old and pointless now especially on a laptop
turn off the acpi battery...

Why do you say we shouldn't turn off the core parking on desktop workstations?
 

He says in the quote it's old and pointless as far as I can see.

I agree.

Jonbouy

Freddie H

jcschild


do not do it period.. its old and pointless now especially on a laptop
turn off the acpi battery...

Why do you say we shouldn't turn off the core parking on desktop workstations?

He says in the quote it's old and pointless as far as I can see.

I agree.

Old or not its sill a huge difference in performance ON or OFF. I have it disabled! I don't use and you shouldn't use SpeedStep, C-State either. Full POWER no eco b-ulls-h-i-t- mode. No ECO on graphic card either! That is the default setting for any computer!
 
My two cents 

Freddie H

Jonbouy

Freddie H

jcschild


do not do it period.. its old and pointless now especially on a laptop
turn off the acpi battery...

Why do you say we shouldn't turn off the core parking on desktop workstations?

He says in the quote it's old and pointless as far as I can see.

I agree.

Old or not its sill a huge difference in performance ON or OFF. I have it disabled! I don't use and you shouldn't use SpeedStep, C-State either. Full POWER no eco b-ulls-h-i-t- mode. No ECO on graphic card either! That is the default setting for any computer!
 
My two cents 

I've tested at this end, and the only benefit I got was more pops and clicks along with higher CPU temps and increased fan noise as a result with no discernable performance improvements at all.

What can I say?

"Freddie H"
Old or not its sill a huge difference in performance ON or OFF. I have it disabled! I don't use and you shouldn't use SpeedStep, C-State either. Full POWER no eco b-ulls-h-i-t- mode. No ECO on graphic card either!

I agree (dedicated desktop DAWs only).

"Jonbouy"
I've tested at this end, and the only benefit I got was more pops and clicks along with higher CPU temps and increased fan noise as a result with no discernable performance improvements at all.

I believe it's very important to make a distinction between laptops and desktops. Core parking on laptops is needed to help manage heat. I wouldn't mess with it (unless I didn't care about the life span/longevity of important components). But when talking about desktops (dedicated and properly cooled), then all bets are off. I'm a tweaker, and I tweaked the heck out of my DAW, right down to background processes. The benefits are undeniable and I would go so far as to wonder what happened in your case?

For maximum DAW performance:
We don't want the OS/hardware having the ability to "throttle down" speed/performance to save energy.
We don't want the PC "tied up" managing non-essential tasks.

Depending on circumstances, you may "get by" without any tweaks.
For absolute maximum performance (especially when running heavy loads at ultra-low latency settings), tweaks are necessary.

Freddie,
got news for you all that is OLD OLD OLD and not to be done now...

Alegria

"Freddie H"

Old or not its sill a huge difference in performance ON or OFF. I have it disabled! I don't use and you shouldn't use SpeedStep, C-State either. Full POWER no eco b-ulls-h-i-t- mode. No ECO on graphic card either!

I agree (dedicated desktop DAWs only).

"Jonbouy"

I've tested at this end, and the only benefit I got was more pops and clicks along with higher CPU temps and increased fan noise as a result with no discernable performance improvements at all.

I believe it's very important to make a distinction between laptops and desktops. Core parking on laptops is needed to help manage heat. I wouldn't mess with it (unless I didn't care about the life span/longevity of important components). But when talking about desktops (dedicated and properly cooled), then all bets are off. I'm a tweaker, and I tweaked the heck out of my DAW, right down to background processes. The benefits are undeniable and I would go so far as to wonder what happened in your case?

Sorry, read up, the thread was about core parking, the clue is in the title, that's what I'm referring to, I've tweaked for sure, but only where there is a benefit.  Disabling core parking isn't an area that provided any.

Jim Roseberry


For maximum DAW performance:
We don't want the OS/hardware having the ability to "throttle down" speed/performance to save energy.
We don't want the PC "tied up" managing non-essential tasks.

This ^^^^

I run 64 samples buffer all day long easily even with the biggest loads I ever get up to.  No glitches, no pops, no crashes and a clean error log and power to burn.

I'm not bothered what anyone else does but I love my setup as it is.

Freddie, Alegria please show me where I've got it all wrong?  I'm all ears.

"Jonbouy"
Sorry, read up, the thread was about core parking, the clue is in the title, that's what I'm referring to

Excuse me? I may have thrown in a general comment in my reply, but the context was about core parking.

"Jonbouy"
I've tweaked for sure, but only where there is a benefit. Disabling core parking isn't an area that provided any.

Well then, the point is moot. And that was not my experience btw.

"Jonbouy"

"Jim Roseberry"
For maximum DAW performance:
We don't want the OS/hardware having the ability to "throttle down" speed/performance to save energy.
We don't want the PC "tied up" managing non-essential tasks.

This ^^^^

I gather you agree with this (as do I). Then, what is your definition of core parking???

I gather you agree with this (as do I). Then, what is your definition of core parking???

"Core parking is a new feature that Microsoft introduced in Windows 7 and Windows Server 2008 R2. Depending on the resource use of the operating system it may park one or multiple cores of a multi-core cpu to reduce the computer’s power consumption and thermal emissions. Once operations require more processing power, the parked cores are activated again to assist in the tasks."

Surely you should already know this if you are tweaking it...

Do you also need info on Hyperthreading, EIST and C states while I'm about?

hehehe..., you're so cute. 

Jonbouy

I gather you agree with this (as do I). Then, what is your definition of core parking???

"Core parking is a new feature that Microsoft introduced in Windows 7 and Windows Server 2008 R2. Depending on the resource use of the operating system it may park one or multiple cores of a multi-core cpu to reduce the computer’s power consumption and thermal emissions. Once operations require more processing power, the parked cores are activated again to assist in the tasks."

Surely you should already know this if you are tweaking it...

Do you also need info on Hyperthreading, EIST and C states while I'm about?

You have answer it yourself there.

You don’t need to be rocket scientist to understand if you park something, shutting anything off, it will decrease the performance. Drive V8 engine on only 4 cylinders doesn’t exactly increase its performance. Even a child understands that.
 
When having C state, core parking or whatever activated makes very bad impact on any computers performance. As for an example what happens in DAW is that the core that is “park mode”, “C1 sleep” can’t wake up in time when you hit “play” when suddenly the computer needs all its CPU resources. C1 lower the CPU clock meaning slower performance.
One of the side effects that happen if you do have the core park, C1 sleep mode is that you get drop outs and clicks in the audio. Sometimes this can even cause blue screen death in rare cases.
 
 
Microsoft green eco movement politics infinitum madness!
I like to stop global warming, ecologic when it comes to food, light, lower gas on cars or whatever but not when it’s all about my work computer and performance in the studio. It is better they; Microsoft, Intel, Samsung and rest of companies focus on something’s else;----> lower overall power consumption instead of lower the overall performance of our system and CPU:s.

 

Freddie H


You have answer it yourself there.

You don’t need to be rocket scientist to understand if you park something, shutting anything off, it will decrease the performance. Drive V8 engine on only 4 cylinders doesn’t exactly increase its performance. Even a child understands that.

Freddie you are not even a child then, if an engine manufacturer could make a V8 use 4 cylinders when it's idling they would, it doesn't affect performance when the gas pedal is on the floor and all cylinders are delivering full power when needed.

 
When having C state, core parking or whatever activated makes very bad impact on any computers performance. As for an example what happens in DAW is that the core that is “park mode”, “C1 sleep” can’t wake up in time when you hit “play” when suddenly the computer needs all its CPU resources. C1 lower the CPU clock meaning slower performance.
One of the side effects that happen if you do have the core park, C1 sleep mode is that you get drop outs and clicks in the audio. Sometimes this can even cause blue screen death in rare cases.

If this is true why am I not getting blue screens pops and clicks when I press play?  I can run a 48 samples buffer under a reasonable load without glitching, I choose to run 64 samples and can live with the 7 ms RTL without having to change settings when I change from tracking to mixing.  What do I need to fix again? 
 

Microsoft green eco movement politics infinitum madness!
I like to stop global warming, ecologic when it comes to food, light, lower gas on cars or whatever but not when it’s all about my work computer and performance in the studio. It is better they; Microsoft, Intel, Samsung and rest of companies focus on something’s else;----> lower overall power consumption instead of lower the overall performance of our system and CPU:s.

Choosing the Windows 'High Performance' power plan effectively overides EIST anyway base a plan on that turning off all the going to sleep or hibernate nonsense and you've pretty much done all that's required.

Benchmark your CPU with Core Parking enabled/disabled, C1E (bios) on/off, and then SpeedStep on/off (you'll find that is overridden by the power plan anyway). 

Show us the different results in actual figures because here there isn't anything to support turning them off.  The only thing that would alarm me is from going from idle to full power if that was manifesting in glitches.  It doesn't.

Post #8 in this thread explains it well and highlights the more obvious areas of concern.  Some people are cranky enough to hack the registry to get the cores from parking but then install and run the ASUS AISuite, which is a far more evil performance killer than processor core wake times.  I hope you're not one of those Freddie!

One final note, just for kicks try benchmarking some stuff with hyperthreading turned off so you are restricted to just the 4 physical cores.  The results there might surprise you especiallly on stuff  that uses a lot of floating point calculations.

Me, I did all that at build time, now I'd just rather get on and enjoy using my machine.
 

Eek! This thread is getting too technical for me.

Hmm, "Core Eject", wonder what that button does...

Goddard


Eek! This thread is getting too technical for me! 

I doubt it.

More like you can't afford to expend the energy on a 10,000 word dissertation just now...

Oh wait, I completely overlooked Windows "Core Audio" APIs...

Jonbouy

Freddie H


You have answer it yourself there.

You don’t need to be rocket scientist to understand if you park something, shutting anything off, it will decrease the performance. Drive V8 engine on only 4 cylinders doesn’t exactly increase its performance. Even a child understands that.

Freddie you are not even a child then, if an engine manufacturer could make a V8 use 4 cylinders when it's idling they would, it doesn't affect performance when the gas pedal is on the floor and all cylinders are delivering full power when needed.

When having C state, core parking or whatever activated makes very bad impact on any computers performance. As for an example what happens in DAW is that the core that is “park mode”, “C1 sleep” can’t wake up in time when you hit “play” when suddenly the computer needs all its CPU resources. C1 lower the CPU clock meaning slower performance.
One of the side effects that happen if you do have the core park, C1 sleep mode is that you get drop outs and clicks in the audio. Sometimes this can even cause blue screen death in rare cases.

If this is true why am I not getting blue screens pops and clicks when I press play?  I can run a 48 samples buffer under a reasonable load without glitching, I choose to run 64 samples and can live with the 7 ms RTL without having to change settings when I change from tracking to mixing.  What do I need to fix again? 

Microsoft green eco movement politics infinitum madness!
I like to stop global warming, ecologic when it comes to food, light, lower gas on cars or whatever but not when it’s all about my work computer and performance in the studio. It is better they; Microsoft, Intel, Samsung and rest of companies focus on something’s else;----> lower overall power consumption instead of lower the overall performance of our system and CPU:s.

Choosing the Windows 'High Performance' power plan effectively overides EIST anyway base a plan on that turning off all the going to sleep or hibernate nonsense and you've pretty much done all that's required.

Benchmark your CPU with Core Parking enabled/disabled, C1E (bios) on/off, and then SpeedStep on/off (you'll find that is overridden by the power plan anyway). 

Show us the different results in actual figures because here there isn't anything to support turning them off.  The only thing that would alarm me is from going from idle to full power if that was manifesting in glitches.  It doesn't.

Post #8 in this thread explains it well and highlights the more obvious areas of concern.  Some people are cranky enough to hack the registry to get the cores from parking but then install and run the ASUS AISuite, which is a far more evil performance killer than processor core wake times.  I hope you're not one of those Freddie!

One final note, just for kicks try benchmarking some stuff with hyperthreading turned off so you are restricted to just the 4 physical cores.  The results there might surprise you especiallly on stuff  that uses a lot of floating point calculations.

Me, I did all that at build time, now I'd just rather get on and enjoy using my machine.

Whatever...You should try the opposite and activate the performance of your system.
What's next on your list that you try to convince us? A 32bit application can use more RAM then x64?

You are not listening Freddie, like I said I've already tested thoroughly.

I'm not trying to convince anyone of anything just telling you straight my own findings on the subject, you are the one that goes around trying to convince people that BS is fact and what you say is what they shoud do remember?  Not me.

btw I'd recommend still using 32 bit versions rather than use bridging solutions unless your project does require the extra RAM.  I still see people putting up with countless issues caused by bridging when the project size doesn't even warrant opening a 64 bit project.  Go figure.

I do enjoy having the benefits of 64 bit though...

Out of curiosity Jon as I don't recall you mentioning it, is your system dedicated for audio only?

It is optimised for DAW performance.

Sure, I do other stuff with it though.

It was concieved as a collaboration between myself and a successful PC builder to add to his range of PC's and was designed for maximum Audio performance on a low budget.

We were not aiming for cutting edge producers more for the enthusiast on a budget (someone just like me and many others here), hence going with the H67 to use the 3000 graphics on the 2600 chip, we succeded.  He was retailing those boxes a year ago to the same spec for £500 and they were trumping £1200 offerings from other manufacturers.

So it was built to a specification, and fits that specification perfectly.  I'm always a long way off maxing it out.  Sure you can spend more money for a bit more performance if you need it but what's the point just for the sake of it?

Get something that exactly fits your particular needs and get the most out of it, or get into some kind of competition where you get the latest and greatest at a premium price so you can brag on a forum about theoretical figures.  It's a free choice.

Does that answer your transparently obvious question?  Dedicated for DAW only....LOL!  I need a working tool not a shrine matey...

Add to that, you've also got a dedicated builder, a top end dedicated DAW builder too, here telling you as well you don't need to piddle about with all that 'Core Parking' garbage anymore and still you are trying to convince everyone you've got it right.

Post the figures to prove it.  It's easy enough to do.  Rather it would be if there was any discernable improvement.

Take that stupid AISuite off too, it has two buggy drivers that are known performance killlers and runs background tasks that serve no useful purpose.  It diminishes Audio performance far more than 'Core Parking' does.  If you need to watch guages and thermometers displaying numbers then get something that only runs when you double click it to do the job...

"Jonbouy"
It is optimised for DAW performance.

Sure, I do other stuff with it though.

It was concieved as a collaboration between myself and a successful PC builder to add to his range of PC's and was designed for maximum Audio performance on a low budget.

We were not aiming for cutting edge producers more for the enthusiast on a budget (someone just like me and many others here) ...

<sarcasm free zone>Now that's pretty darn cool to involve yourself in such a project. A win-win for all involved, and I'm sure you and your PC builder made many musicians day so to speak by giving them access to a "high-end like" DAW at a amazing price.</sarcasm free zone>

"Jonbouy"
Get something that exactly fits your particular needs and get the most out of it, or get into some kind of competition where you get the latest and greatest at a premium price so you can brag on a forum about theoretical figures. It's a free choice.

Of course, that's the goal, although I fail to grasp the pertinence of the 2nd part of your 1st sentence. Is there a message in there for someone in particular?

"Jonbouy"
Does that answer your transparently obvious question? Dedicated for DAW only....LOL! I need a working tool not a shrine matey...

The fact that I'm demanding of the tools I chose to work with has nothing to do with religion, shrines and rhymes. The fact that you also use your machine for non-audio related tasks, makes it much more difficult/unwise/impossible for you to optimize/streamline/tweak your machine as I would mine. The fact that you overclock your machine, albeit reasonably, makes it unwise for you to turn off core parking. It's all about choice, I completely agree. And these facts don't make you or me bigger/longer/holier than the other, matey. We obviously have different needs and budget to meet those needs.

"Jonbouy"
Add to that, you've also got a dedicated builder, a top end dedicated DAW builder too, here telling you as well you don't need to piddle about with all that 'Core Parking' garbage anymore and still you are trying to convince everyone you've got it right.

Well, I've noticed Scott mention this for the first time in this thread and as a reply to the OP, not me. I don't agree btw. And I don't recall Jim mentioning anything at all to that effect. Who's trying to convince who again? You are the only one that erroneously perceives my opinion as trying to convince everyone. And who's everyone. That's a pretty broad statement, don't you think? The bottom line here is clear to me and since you're so..., liberal about the "everyone" card, let me have a go at it also.

Treating everyone that ain't you or a pro DAW builder as ignorant fools that don't know any better..., doesn't make it so. Just as you have achieved your goals within your budget and specifications (which you have so proudly elaborated for everyone's benefit), so have I. And I'm talking about the "holy grail". Something I haven't seen you mention at all. DPC latency. And it's not so much the fact that I've achieved border line single digit numbers in a Win 7 environment (I could easily live with higher numbers), it's the fact that it's a flat line no matter how long the utility is used for. Completely spikeless. And that's what has allowed me to enjoy EastWest's QL Pianos for example in a stable, solid and reliable environment, consistently day in and day out. And disabling core parking was "a component" of the process that helped me achieve this. I'm just as proud about it as you are about yours. Scott and/or Jim is more than welcome to elaborate on the futility of disabling core parking in a dedicated DAW context. I'm all ears..., and good luck in trying to convince me otherwise.

"Jonbouy"
Take that stupid AISuite off too, it has two buggy drivers that are known performance killlers and runs background tasks that serve no useful purpose. It diminishes Audio performance far more than 'Core Parking' does. If you need to watch guages and thermometers displaying numbers then get something that only runs when you double click it to do the job...

Now now Jon, you're assuming again and being a poor sport (grown men don't act this way). And a Freudian slip to boot. Priceless!

""Well, I've noticed Scott mention this for the first time in this thread and as a reply to the OP, not me. I don't agree btw. And I don't recall Jim mentioning anything at all to that effect. """

you dont agree really? are you on an X58 or beyond.. X58 see this thead.
http://www.gearslutz.com/board/music-computers/465221-c1e-c3-c6-eist-speedstep-turbo-boost-core-parking.html

if you are on 1155 or 2011 then forget every bit of it..

UMM yes Jim most certainly said the same..
 
and i would echo the request post the benchmarks.... as i can prove it..

1155...

"jcschild"
Core parking: since this so far only seems a potential (not definitive) issue for Sonar i wont say much. (its also only for Sonar) its Hyper-threading way of doing C1E if there are not enough threads
required it will "park" shut down the HT cores to a ready but not active state. (Win 7 only). Core parking is supposed to be an efficient way of data caching with concern to HT as well. With Core parking enabled it can cause threading issues in Sonar.

All of this power management is supposed to be about "Green" frankly if i want to save energy i will lower my heat and put a sweater on.
 for DAWs ideally you would turn all of this off and have 100% access to full power at all times. leaving it on can cause issues particularly low latency power users.

Seems to me like we do agree about the benefits of disabling core parking, especially in a dedicated DAW context. Thanks Scott! 

He said 1155 or 2011 then foget every bit of that.

Shall I post an old quote where you are using AISuite to update the BIOS as well then Alegria?  I assume nothing!

You really are beyond belief, after several tests I've finally decided.

Hey Jon,
are you sure he is using asus ai suite? as much as a PITA he can be i think he is far smarter than that?

Ai suite= not too bright...

jcschild


Hey Jon,
are you sure he is using asus ai suite? as much as a PITA he can be i think he is far smarter than that?

Ai suite= not too bright...

He certainly was at one point.  He may deny it now though, he said I was assuming that just now but he actually posted about it...

Careful with that 'smart' word btw, especially if you combine it with 'alec', it's been known to cause weeping before...

"Jonbouy"
He may deny it now though, he said I was assuming that just now but he actually posted about it.

There's no need for me to revisit this as all my posts are public and usually non-edited (contrary to yours). We've had this conversation before and a quick search would put your misleading comments about the Asus AI suite to rest. Next...

And I would appreciate a reply to my post #32, if you will. Oh, and the topic was/is about core parking. Remember? 

"Jonbouy"
He said 1155 or 2011 then foget every bit of that.

I know what he said and simply followed the link he provided. If there was a particular post of his he wanted to emphasize, then linking to said post is a simple affair and the least he can do. I have better things to do then to go through 6 pages of back and forth confrontational opinions about C-States. Have you noticed that about Scott? Confrontation and confusion seems to follow him around quite a bit. And that's an observation, no more no less.

@ Scott
Quid Pro Quo dude. 

all my posts are public and usually non-edited (contrary to yours).

Are you inferring something other than I have fat fingers?

btw Core Parking is no longer needed or desired.  Just so you know so you can change your stance on it just like you did when I pointed out to you that AISuite was a pile of poop.

To be fair you usually get there in the end.
 

Alegria

And I would appreciate a reply to my post #32, if you will. Oh, and the topic was/is about core parking. Remember? 

You asked a question in that post?

Ah yes I found it I think.

    Alegria

        "Jonbouy"

        Get something that exactly fits your particular needs and get the most out of it, or get into some kind of competition where you get the latest and greatest at a premium price so you can brag on a forum about theoretical figures. It's a free choice.

    Of course, that's the goal, although I fail to grasp the pertinence of the 2nd part of your 1st sentence. Is there a message in there for someone in particular?

Yes, Alegria that would be you then.

Alegria


Something I haven't seen you mention at all. DPC latency. And it's not so much the fact that I've achieved border line single digit numbers in a Win 7 environment (I could easily live with higher numbers), it's the fact that it's a flat line no matter how long the utility is used for.

Sorry, I must dash I gotta go and impress my GF with my DPC latency figures...oh my.

Alegria


I know what he said and simply followed the link he provided. If there was a particular post of his he wanted to emphasize, then linking to said post is a simple affair and the least he can do. I have better things to do then to go through 6 pages of back and forth confrontational opinions about C-States. Have you noticed that about Scott? Confrontation and confusion seems to follow him around quite a bit. And that's an observation, no more no less.

the very first post was all you had to read. the point to it is very simple.
 
IF you are not on X58 or 1156 socket
 
then all of that stuff that once needed to be done (and FYI core parking was specific to Sonar only and was pretty useless, rarely fixing anything)
is no longer needing to be done..
 
there is much tweaking to still do yes in win7 as few items in bios (far far less than XP ) but C states/core parking etc or disabling anything that stops full power use including hyperthreading
is well STUPID
 
i fail to see the confusion of that statement or for that matter any of my statements.. feel free to enlighten me so i can set you stright..
 
do you even know what Quid pro quo means.. rather out of context here..

Jim Roseberry


For maximum DAW performance:
We don't want the OS/hardware having the ability to "throttle down" speed/performance to save energy.
We don't want the PC "tied up" managing non-essential tasks.

Depending on circumstances, you may "get by" without any tweaks.
For absolute maximum performance (especially when running heavy loads at ultra-low latency settings), tweaks are necessary.

quoted for algeria benefit..

jcschild

quoted for algeria benefit..

I'm waiting for him to post the performance benefit he get in figures....

Alegria

"Jonbouy"
 I have better things to do then to go through 6 pages of back and forth confrontational opinions about C-States. Have you noticed that about Scott? Confrontation and confusion seems to follow him around quite a bit. And that's an observation, no more no less.

No actually the reverse is true Alegria, I've found Scott's opinions are mostly backed up with sound factual data.  I get more confused by your confrontational style when you make blanket statements that can't be backed up and you start to act like a smart alec.  That was the observation, no more no less, I made about you a few weeks back when you got all hurt and affronted by it and started crying breach of TOS statements.

Some of your inferences that you've made here and elsewhere are purely confrontational however you might like to think you've cleverly veiled them.  If I think something I'll tell ya!

so there is no confusion..
i must speak engrish and type chineese or something.

for socket 2011 and 1155
in the bios (for those who would be confused)

Hpet OFF..   (there is my bonus tip for the week)

all cstates ON, turning any of these off stops turbo mode.. never mind OCing..
hyper threading on..

anything else is again STUPID..

oh wait there muight be some confusion so i guess i better be completely clear..

this does not count other bios tweaks just those concerning cstates
ram timing etc is a completely differnt discussion..

Alegria has a MemOK button and he knows how to press it...

jcschild


so there is no confusion..
i must speak engrish and type chineese or something.

for socket 2011 and 1155
in the bios (for those who would be confused)

Hpet OFF..   (there is my bonus tip for the week)

all cstates ON, turning any of these off stops turbo mode.. never mind OCing..
hyper threading on..

anything else is again STUPID..

oh wait there muight be some confusion so i guess i better be completely clear..

this does not count other bios tweaks just those concerning cstates
ram timing etc is a completely differnt discussion..

Thanks for making that clear. So anyone that do not use 2011 and 1155 should disable all!

read the thread i linked to.. but yes basically other than HT

Freddie H


Thanks for making that clear. So anyone that do not use 2011 and 1155 should disable all!

Only if your DAW is DEDICATED by a papal order bestowed on it by Alegria.  Using Notepad is prohibited.

Fair play Freddie at least you listen and are always good humoured about it...

Jonbouy

Freddie H


Thanks for making that clear. So anyone that do not use 2011 and 1155 should disable all!

Only if your DAW is DEDICATED by a papal order bestowed on it by Alegria.  Using Notepad is prohibited.

Fair play Freddie at least you listen and are always good humoured about it...

 
Yeah Sure..
About english humor. Who is the man of the picture of your avatar? It looks kind of funny.
 
(Note: If its picture of you, please don't be offended, that is not my attention.)

LOL

He's called Terry Tibbs and he likes to buy and sell things....

What we'd call a 'wide boy' over here.

Google him.

Jonbouy


LOL

He's called Terry Tibbs and he likes to buy and sell things....

What we'd call a 'wide boy' over here.

Google him.

all this time i thought it was telly savalis

jcschild

for socket 2011 and 1155
in the bios (for those who would be confused)

Hpet OFF..   (there is my bonus tip for the week)

Oh good grief, not again...

Somehow, after the announcement of Billy's passing, and out of respect for those who are mourning (including his friends here), I'll pass on commenting for now (I'll be back in a few days). Feel free to continue knocking yourselves out in the meantime.

I'm not even going to comment on that other than to say you've just been blocked for good.

Goddard

jcschild

for socket 2011 and 1155
in the bios (for those who would be confused)

Hpet OFF..   (there is my bonus tip for the week)

Oh good grief, not again...

oh feel free to explain.. i will gladly hand you your butt

jcschild

Goddard

jcschild

for socket 2011 and 1155
in the bios (for those who would be confused)

Hpet OFF..   (there is my bonus tip for the week)

Oh good grief, not again...

oh feel free to explain.. i will gladly hand you your butt

No, please, I insist, you first. Your bonus tip, after all. Don't leave us all guessing as to why we should turn off HPET.


Were you implying that HPET somehow has something to do with core parking or power or performance management? Or was it merely a general system performance improvement tip? Or what?

Jonbouy


LOL

He's called Terry Tibbs and he likes to buy and sell things....

What we'd call a 'wide boy' over here.

Google him.

Got it!

"Jonbouy"
I'm not even going to comment on that other than to say you've just been blocked for good.

I'll try to get over it. 

"jcschild"
do you even know what Quid pro quo means.. rather out of context here..

It was a reference to an older debate we've had, where you simply avoided answering a very specific question (you took your ball and went home, remember?). So if you have any hard numbers to show that would put to rest this debate about core parking, my suggestion at this point is to..., show them. That's it, that's all.

Note 1: As for the "easy button", where can I get me one of those?

Note 2: As for the "HPET" pseudo-tweak, I've asked the question a long time ago about the benefits of leaving it ON or OFF. Never got an answer, but after approx. 3 months of having it OFF, I'm in a better position to make up my own mind. I'll be glad to share what I've discovered..., after you've answered "Goddard's" question of course.

Hpet:  in a nut shell so all can understand

You turn that off because it allows the C state changes to happen at a much faster interval. It also allows Drivers to interrupt the CPU every 1ms instead of 10 ms.