[5184] L8 uses 30% more CPU than L7

[Kodama]

Tone - u ok there?

Discussion and disagreement are good things., but it seems like last week you lost all ability to have a discussion without resulting to insults.

[Tone Deft]

no, having a great week, just coming across different. it's just the interweb, assholes and pedophiles.

it's funny when work meets hobby, some of us have very definite philosophies on beta testing. imagine if Live was cooking vegan soup, you'd get passionate about how they did it.

[Kodama]

Ha! I wish my job was making soup instead of making a website about something I could care less about today.

I have a really good tortilla soup recipe.

[Tone Deft]

oh man, now you got me... tortilla soup!! we had some amazing tortilla soup in Mexico and haven't found a decent bowl since.

I assume you don't do a chicken broth base I gotta ask what your recipe is.

[slirak]

wow.

anyone else want to address señor limpdick?

Aw, come on - you wouldn't expect me to be able to wave it if it was all stiff and hard, would you?

Anyway, all this wavin' made me forget the actual point.

I'm not worried that the performance hit is down to a bug. If I was, I'd be posting it as such, in the beta bug forum. I'm worried that it's not.

L8 isn't in early beta anymore. I wouldn't be surprised if it's released in a couple of weeks. So I'm a bit worried that this pretty large performance hit is due to neither a bug nor debugging routines and that L8 simply will be even more CPU hungry than L7. The CPU consumption has IMO been Live's biggest flaw for years.

I'm not very worried though. Just an itsy-bitsy teenie weenie bit.

[Dalibor Loncar]

i compared the cpu performance with tarekith´s test, no more than 7 % increase of cpu power consumption

http://forum.ableton.com/viewtopic.php? ... 99#p863599

i will now check if live´s cpu meters are telling the truth ...

[db91977]

I'm sure the Abletons are hearing our performance concerns. If for no other reason, to maximize their sales, I'm sure they will do everything possible to address these concerns. To me, this is stating the obvious, but when we get bogged down in details, sometimes it pays to step back and take a look at the big picture.

--Doug

[flogistox]

so far the cpu issue stopped me doing the beta testing: on my macbook with leopard fan starts to go to full speed even using few tracks (no matter if audio or midi). i noticed that while the live cpu monitoring doesn't show it, looking at the main monitoring of leopard live drains a lot of cpu power, a clear sign that something is going on under the hood, hopefully just related to the beta phase

[bulo]

From Live's Manual, page 486:

"Note that the CPU
meter takes into account only the load from processing audio, not other tasks the computer
performs (e.g., managing Live's user interface). "

so...

[glitchrock-buddha]

From Live's Manual, page 486:

"Note that the CPU
meter takes into account only the load from processing audio, not other tasks the computer
performs (e.g., managing Live's user interface). "

so...

So that's why Live craps out at around 80% cpu use, which we've all come to expect, and that's fine.

The issue we're concerned with is that the beta of Live 8 currently uses 80% cpu on a set that used to use 60% cpu on the same computer with Live 7.

[bulo]

bulo wrote:
From Live's Manual, page 486:

"Note that the CPU
meter takes into account only the load from processing audio, not other tasks the computer
performs (e.g., managing Live's user interface). "

so...


So that's why Live craps out at around 80% cpu use, which we've all come to expect, and that's fine.

The issue we're concerned with is that the beta of Live 8 currently uses 80% cpu on a set that used to use 60% cpu on the same computer with Live 7.

I've just notice that the french translation don't say the exact same thing, and I first read this in the french manual before copy/paste it in the english one to put it here. In the french one, it doesn't say the "the other COMPUTER tasks", but just "the other tasks", what we would understand as "the other tasks Live is managing".

[paq]

I've just notice that the french translation don't say the exact same thing, and I first read this in the french manual before copy/paste it in the english one to put it here. In the french one, it doesn't say the "the other COMPUTER tasks", but just "the other tasks", what we would understand as "the other tasks Live is managing".

It's the same, isn't it? The CPU Meter indicates CPU load by processing audio. All other operations are not taken account.

CPU hunger of Live 8 definitely is a problem, but for me it has become better with last betas. I have got a set with tons of operators in it (bassdrum + drumkit + organ + organ + bass sound + noise). the organs are plugged with multiband effects - this is terrible, because there are 3 ops per organ running with different effects - one organ playing drives cpu meter up to 60%!! (on a 3GHZ DUAL CORE!!!)

But multicore-support was worse in early beta. There my pc wasn't able to run that set. Now it works, because the cores are well balanced. [edit: the second organ indeed is freezed. without this it wouldn't be possible at all, at cpu peaks i get small glitches]

A friend of mine could not run the set, because he has got 4 core Intel with just 2,4ghz each. If you do Multiband-effect-Operators, i think they are always processed on the same core. Quite hard.

I hope, ableton will engage a programmer just for mathematically optimizing their codes. But I don't believe much will be done until release of 8... time is running, and there are too many bugs to fix.

[evon]

wow.

anyone else want to address señor limpdick?

Aw, come on - you wouldn't expect me to be able to wave it if it was all stiff and hard, would you?

Anyway, all this wavin' made me forget the actual point.

I'm not worried that the performance hit is down to a bug. If I was, I'd be posting it as such, in the beta bug forum. I'm worried that it's not.

L8 isn't in early beta anymore. I wouldn't be surprised if it's released in a couple of weeks. So I'm a bit worried that this pretty large performance hit is due to neither a bug nor debugging routines and that L8 simply will be even more CPU hungry than L7. The CPU consumption has IMO been Live's biggest flaw for years.

I'm not very worried though. Just an itsy-bitsy teenie weenie bit.

+1..I feel good everytime mr. Dick watcher gets licked

[Tone Deft]

wow.

anyone else want to address señor limpdick?

Aw, come on - you wouldn't expect me to be able to wave it if it was all stiff and hard, would you?

Anyway, all this wavin' made me forget the actual point.

I'm not worried that the performance hit is down to a bug. If I was, I'd be posting it as such, in the beta bug forum. I'm worried that it's not.

L8 isn't in early beta anymore. I wouldn't be surprised if it's released in a couple of weeks. So I'm a bit worried that this pretty large performance hit is due to neither a bug nor debugging routines and that L8 simply will be even more CPU hungry than L7. The CPU consumption has IMO been Live's biggest flaw for years.

I'm not very worried though. Just an itsy-bitsy teenie weenie bit.

+1..I feel good everytime mr. Dick watcher gets licked

ease up their Chief, it's not for you to say. I was just letting the guy know I was one of his peers, he's cool, he didn't take the troll bait and just moved on with a sense of humor. for all we know he and I were in some of the same classes or have worked together.

dunno where you fit into all of it.

[evon]

[quote="Tone Deft]
dunno where you fit into all of it.[/quote]

Well keep it off here will you. This is a public forum! You just cant help getting yourself deeper and deeper in it, can you?
Apart from learning about coding you should also learn about being cool from this guy.