Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Memory access on G5s again
Last post Fri, Jun 24 2005 by Nick Batzdorf, 27 replies.
Options
Go to last post
2 Pages12>
Posted on Wed, May 04 2005 05:45
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
I have 5GB in my new dual 2.5, and I'm able to load about 2.6GB of samples (not VSL - don't have the HD in there yet) before Logic goes boom.

Have I done anything to deserve less than the 3GB other people are reporting? [Indifferent]
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Wed, May 04 2005 10:20
by aristote797
Joined on Mon, Sep 13 2004, Posts 61
I don't undestand the problem of somebody about this difference (2,6 -3 Go RAM)

My configuration is almost the same than yours: G5 dual 2,5 with 5,5 Go of RAM. I'm working with Logic, 60 EXS, and the Komplete2 from Native I. Several DD ext Fire Wire with VSL.

And I can load up to 3,02 -3,05 Go (as I can see on the "Monitor").

Une explication ?

Aristote the frenchie.
Posted on Wed, May 04 2005 11:38
by PaulR
Joined on Mon, Dec 22 2003, England, Posts 2371
Nick Batzdorf wrote:
I have 5GB in my new dual 2.5, and I'm able to load about 2.6GB of samples (not VSL - don't have the HD in there yet) before Logic goes boom.

Have I done anything to deserve less than the 3GB other people are reporting? [Indifferent]


Which version of Logic Nick? I'm still on 6.4 and get over 3 gigs using VSL. Admittedly I never really use that many tracks that much, so I would have to do another test. I would have thought that if your'e on Logic 7.1 now it's available, you would have got about another 1/2 a gig approximately. The clock speed wouldn;t make that much difference i.e. 2.0 v 2.5 would it?
Posted on Thu, May 05 2005 23:52
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
7.01, and it's actually 2.71GB. Also, Logic doesn't go BOOM, it just hangs.

I wonder whether I have a bad memory chip, and I'm not sure how to check.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Thu, May 05 2005 23:53
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
7.01, and it's actually 2.71GB. Also, Logic doesn't go BOOM, it just hangs.

I wonder whether I have a bad memory chip, and I'm not sure how to check.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Sun, May 08 2005 04:29
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
Today it went BOOM.

This is very annoying. I'm going to try a total clean install on a FW drive and see whether it does the same thing.

And my machine came without the hardware testing CD, so I can't even run it to see whether the memory is bad (if that test is thorough enough to really tell you).

Edit: I got it to load 3.15GB of VSL (total as shown in Activity Monitor), but as soon as I tried sequencing something it crashed.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Sun, May 08 2005 17:10
by PaulR
Joined on Mon, Dec 22 2003, England, Posts 2371
Nick Batzdorf wrote:
Today it went BOOM.

This is very annoying. I'm going to try a total clean install on a FW drive and see whether it does the same thing.

And my machine came without the hardware testing CD, so I can't even run it to see whether the memory is bad (if that test is thorough enough to really tell you).

Edit: I got it to load 3.15GB of VSL (total as shown in Activity Monitor), but as soon as I tried sequencing something it crashed.


Unfortunately mate, this is all too commonly reported at the moment. It could be a faulty memory chip, but I doubt it. There are still many reported bugs as you probably well know with Tiger and Logic 7.1. Sad
Posted on Sun, May 08 2005 23:13
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
This is Panther and 7.01 or 7.1, Paul.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Mon, May 09 2005 07:12
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
Well, Apple Hardware Test's long test version says everything's okay. I'm going to believe it for now.

Next step: changing the RAM order - moving the two original 512MB chips outside the four 1GB ones so they're in slots 5&6 instead of 1&2.

The step after that: installing Panther and Logic only on a virgin drive.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Tue, May 10 2005 00:49
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
I hate computers. Sad

3.15GB, and then crash when loading more.

Rearranged RAM, virgin hard drive and OS X and Logic installation. Same thing.

Do I have a hardware problem, or is this just the open files issue I'm running into?

http://community.vsl.co.at/viewtopic.php?t=1541&start=0
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Tue, May 10 2005 03:03
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
3.15GB is actually very good, of course. I just don't want to find out that there's something wrong down the road when all the warranties have worn off.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Tue, May 10 2005 08:09
by PaulR
Joined on Mon, Dec 22 2003, England, Posts 2371
Nick Batzdorf wrote:
This is Panther and 7.01 or 7.1, Paul.


Probably my lack of computer/software technical knowledge here, but does Logic 7.1 run on Panther. Did I hear that it only ran on Tiger?
Posted on Tue, May 10 2005 17:25
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
No, it runs on Panther.

Andrea at Redmatica says i have no problem. I've written to ask him for some clarification (why AM is only showing 3.15 total, when the app space is supposed to be 4GB), but it looks like I can stop worrying. Smile
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Tue, Jun 14 2005 14:27
by plowman
Joined on Sat, Dec 13 2003, Posts 1174
About a month later, I was wondering, Nick, if you've settled into a reliable performance, and if it's now considered a given that 4 Gb of memory yields about 3 Gb of EXS samples on 7.01 running Panther. Many thanks for forging into this frontier.

Also, as someone about to buy memory for a G5 1.8 dual, are there any brand or site suggestions you might have for me? Thanks again.
Posted on Tue, Jun 14 2005 15:11
by dackl
Joined on Sun, Mar 13 2005, New York, NY, Posts 92
Will somebody kindly tell me where the "monitor" is? I can't seem to find it.

I can find "System Performance" window, but that doesn't tell me much.

Thanks very much.
JD
John M. Davis
www.dackl.com
Posted on Tue, Jun 14 2005 16:50
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
Activity Monitor is in the Utilities folder. It's a program. Note that there may be a Heisenberg factor: Activity Monitor itself seems to affect the performance.

Plowman: first of all, the 1.8 only holds 4GB.

And 3GB is overly optimistic. I was able to *load* 3.17GB, but the program would crash as soon as I did anything. A practical limit is about 2.5 - 2.7GB if you want to actually use it.

I bought cheap generic RAM, under the assumption that it takes a fortune to set up a chip factory and there are no Sid in His Living Room outfits - they're all going to be fine.

Question: if you make a warranty claim on something with a lifetime warranty, can the company say, "Sorry, its lifetime is over?"

Smile
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Tue, Jun 14 2005 23:28
by stupid8track
Joined on Thu, Mar 13 2003, Posts 230
IME, the only real, consistent memory limit for logic at the moment is 3.5 GB of Virtual Memory space - once you hit that, logic crashes. unfortunately, there is no way to 'predict' what that will mean in terms of Real Memory. you can make an 'educated guess', though.

when you first open logic, take a look at the difference between real memory and virtual memory for Logic as reported in Activity Monitor and you'll see your max real memory figure (3.5 minus the difference between VM and RM figures as reported in AM).

keep in mind that more Virtual Memory is requested by some plugs, so you always want to leave some headroom. if you're into playing it close, keep AM open and keep an eye on logic's VM allocation.

depending on routings/plugs - you should be able to get around 3 GB. maybe not, but 2.5 seems a little low to me. again - it depends on the requirements of the song and the instruments you want to load.

hope this helps
Posted on Wed, Jun 15 2005 00:41
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
Interesting. When I start Logic I get 505.5MB virtual - 136.99 real = 428.51MB - 3500 = roughly 3.07GB available.

I got my machine up to 3.17GB of real memory before crashing, which is close to what you're saying. But at that point you can't work - the machine slows down like crazy, and it's one breath away from crashing.

Maybe I unloaded too much to make it work, but at 2.75GB it seemed okay. I was being conservative when I said 2.5GB.

Is there any way to increase that? This Autoload has a few Input objects (muted), and 64 empty EXS24s inserted. That's it.
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
Posted on Wed, Jun 15 2005 02:14
by stupid8track
Joined on Thu, Mar 13 2003, Posts 230
nick

i don't know if there is any way to 'close the gap' between VM figure and RM figure upon launch. i can't remember one off the top of my head, but i do remember in testing a long time ago (i believe it was the evan evan's workaround thread - or at least around that time) that i did have 'less' of a gap between VM and RM. but i can't remember if that was something i did or just a function of logic 6.x being less hungry.

also - do you have a program called menumeters? versiontracker has it and it can show you if your system is hitting 'swap' space by creating swap files - perhaps that is part of why you were experiencing such slowness when you got close to 3.5 VM limit?

i wish i could tell you something that is more substantitive, but i'm really not sure how to control memory assignment with logic.

if i get a chance, i'll try to figure out what i might have done to 'reduce' the initial VM memory demand.

the worst part about playing it close to the edge (around 3 GB RM used) is that it is difficult to 'calculate' how much memory a given VSL instrument will use - and that leads to most of my crashes (i think i've got enough room left to load an instrument and i watch Activity Monitor in fear as the VM number goes higher and higher and higher and then... bam.)

thus i agree that a 'safe' figure is somewhere south of 3 GB. or, if you hit 3GB - don't try to load any more instruments - and keep an eye on plugins. some (altiverb sticks in my mind as one, but don't hold me to it) claim 'new' VM space for logic whenever they are inserted. again - sadly i don't have the time to look into it tonight.

i really just wanted to say that, in my experience, 3.5 GB of Virtual Memory space is the 'ceiling' for logic.

hope this helps.
Posted on Wed, Jun 15 2005 04:18
by Nick Batzdorf
Joined on Tue, Apr 29 2003, Los Angeles, Posts 2546
I guess it's kinda silly to obsess about this, especially since I have Giga machines as well - more than I need, actually. The main thing is that I don't want to feel like I'm getting cheated. Smile
Mac Pro 5,1 12-core 3.46 GHz, 64MB RAM, latest macOS available. Metric Halo 2882 interface.

VisionDAW Windows 7 Pro i7 950 3.07 4-core, 24GB RAM. Has an RME Hammerfall HDSP9632, but I just use VE Pro. Also several ancient P4 XP slaves, rarely used.
2 Pages12>
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.