Matlab and large signals - I think I want my money back!
in [Matlab]
|
Prev: Load flow
Next: There are no products to install
From: ImageAnalyst on 19 Feb 2010 13:20 On Feb 19, 12:49 pm, "big data" <bigd...(a)bigdata.com> wrote: > One thing you can do is to implement the 3GB switch in your boot.ini file.. Win32 XP can see 4GB. Normally 2GB is allocated to the kernel and 2GB is allocated to applications. Adding the 3GB line in your boot.ini will allow 1GB to be allocated to the kernel and 3GB allocated to applications. This definitely helped when I was running 32 bit processes using "large address aware" applications like Matlab. > > http://msdn.microsoft.com/en-us/library/ms791558.aspx ------------------------------------------------------------------------------------------------------------------------------------- You can do that, and it might work, but I just thought maybe I would share my experience when doing that. It's not like you're getting an extra gig of RAM for free. Basically you're robbing Peter to pay Paul. So you're taking a gig away from the operating system, and giving it to your app. However I started having bizarre problems, intermittent problems - like gibberish characters on the screen, screens not repainting properly, transparent windows and title bars, etc. We tried getting a new video adapter but the problems remained. I ended up getting a new computer. Only after that did I remove the / 3GB switch and suddenly the problems instantly vanished. I've been using that computer a lot lately (as a "hand me down") and it's still fine. I'm convinced that it was the /3GB switch that was causing me problems. It SHOULDN"T work that way, but how many times have we all said "This just shouldn't be happening... but it is"? Just a warning in advance in case you might notice any weird behaviour.
From: big data on 19 Feb 2010 13:32 ImageAnalyst <imageanalyst(a)mailinator.com> wrote in message <5f2df7b7-c2f0-4894-9d06-197dba2e6623(a)u9g2000yqb.googlegroups.com>... > On Feb 19, 12:49 pm, "big data" <bigd...(a)bigdata.com> wrote: > > One thing you can do is to implement the 3GB switch in your boot.ini file. Win32 XP can see 4GB. Normally 2GB is allocated to the kernel and 2GB is allocated to applications. Adding the 3GB line in your boot.ini will allow 1GB to be allocated to the kernel and 3GB allocated to applications. This definitely helped when I was running 32 bit processes using "large address aware" applications like Matlab. > > > > http://msdn.microsoft.com/en-us/library/ms791558.aspx > > ------------------------------------------------------------------------------------------------------------------------------------- > You can do that, and it might work, but I just thought maybe I would > share my experience when doing that. It's not like you're getting an > extra gig of RAM for free. Basically you're robbing Peter to pay > Paul. So you're taking a gig away from the operating system, and > giving it to your app. However I started having bizarre problems, > intermittent problems - like gibberish characters on the screen, > screens not repainting properly, transparent windows and title bars, > etc. We tried getting a new video adapter but the problems remained. > I ended up getting a new computer. Only after that did I remove the / > 3GB switch and suddenly the problems instantly vanished. I've been > using that computer a lot lately (as a "hand me down") and it's still > fine. I'm convinced that it was the /3GB switch that was causing me > problems. It SHOULDN"T work that way, but how many times have we all > said "This just shouldn't be happening... but it is"? Just a warning > in advance in case you might notice any weird behaviour. Agree 100%. Another area you can run into trouble with /3GB is on networked machines. These days the bloated netware can require the OS to use more than 1GB with all kinds of weird results. What I do with 32-bit machines is add a second line to boot.ini with the /3GB switch. When the machine boots a pre-windows dialog comes up that alllows you to select which line to boot on so you can only use the /3GB switch when you really need it.
From: Mark Shore on 19 Feb 2010 14:10 > You can do that, and it might work, but I just thought maybe I would > share my experience when doing that. It's not like you're getting an > extra gig of RAM for free. Basically you're robbing Peter to pay > Paul. So you're taking a gig away from the operating system, and > giving it to your app. However I started having bizarre problems, > intermittent problems - like gibberish characters on the screen, > screens not repainting properly, transparent windows and title bars, > etc. We tried getting a new video adapter but the problems remained. > I ended up getting a new computer. Only after that did I remove the / > 3GB switch and suddenly the problems instantly vanished. I've been > using that computer a lot lately (as a "hand me down") and it's still > fine. I'm convinced that it was the /3GB switch that was causing me > problems. It SHOULDN"T work that way, but how many times have we all > said "This just shouldn't be happening... but it is"? Just a warning > in advance in case you might notice any weird behaviour. I never noticed any weird behaviour when I tried the /3GB switch, except for the minor issue that the two computers I used it on subsequently failed to boot. Almost too trivial to mention, really...
From: Oleg Komarov on 19 Feb 2010 16:48 Although my working field doesn't have anything to do with signal processing I would give him his money back. I think everybody would gain from that. Oleg
From: Jean on 22 Feb 2010 05:07
Hello, I am still waiting for your answer. "big data" <bigdata(a)bigdata.com> wrote in message <hlmdg3$3k8$1(a)fred.mathworks.com>... > "Jean " <domnul_jan(a)yahoo.com> wrote in message <hlm7d4$oru$1(a)fred.mathworks.com>... > > Although Matlab is an excellent tool in signal processing, it has totally dissapointed me these days when I tried even the SIMPLEST function on large signals (let's say 2.5 million samples or higher). Not only that you must say goodbye to ffts, xcorrs, etc., but even smiple PLOTS cannot be showed because the "OUT OF MEMORY" error appears (in spite of my 4Gb of RAM). > > If you want to "play" research, then Matlab is the perfect tol for you. If you want to do some advanced signal processing o real signals, then orient yourself to another tool. > > Thank you Mathworks for dissapointing me! > > > I run a 64-bit box with 64-bit OS and 64-bit Matlab and 16GB RAM. I routinely work with large datasets right up to 35GB page file size. Matlab is perfectly happy with large data provided you have an adequate computer. > > Coming in here muttering about wanting your money back without having done the most basic research into the subject is lame. You owe TMW an apology. |