https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939476#M14381 <DIV>Hi,</DIV><DIV></DIV><DIV>I am trying to evaluate MKL 8.0 for my large matrix solving project and encountered the following strange behavior. I am using the function cgetrf() and cgetrs() to perform LU decomposition. For small matrix, the code runs fine and pretty fast. However, it seems to me it can not go beyond solving matrix size at about 10000x10000 (single precision complex matrix), even the computer has 2GB memory. A straight copy of code from numerical recipe can solve up to 15kX15k matrix problem on the same machine (although much slower than MKL).</DIV><DIV></DIV><DIV>So my question is</DIV><DIV>1. is this a known problem?</DIV><DIV>2. Is there anyway (such as turn on some flags, etc.) to avoid this "premature" memory limit, even it means some sacrifice of speed.</DIV><DIV></DIV><DIV>Thanks</DIV><DIV></DIV> Thu, 23 Mar 2006 01:06:51 GMT everest 2006-03-23T01:06:51Z https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939476#M14381 <DIV>Hi,</DIV><DIV></DIV><DIV>I am trying to evaluate MKL 8.0 for my large matrix solving project and encountered the following strange behavior. I am using the function cgetrf() and cgetrs() to perform LU decomposition. For small matrix, the code runs fine and pretty fast. However, it seems to me it can not go beyond solving matrix size at about 10000x10000 (single precision complex matrix), even the computer has 2GB memory. A straight copy of code from numerical recipe can solve up to 15kX15k matrix problem on the same machine (although much slower than MKL).</DIV><DIV></DIV><DIV>So my question is</DIV><DIV>1. is this a known problem?</DIV><DIV>2. Is there anyway (such as turn on some flags, etc.) to avoid this "premature" memory limit, even it means some sacrifice of speed.</DIV><DIV></DIV><DIV>Thanks</DIV><DIV></DIV> Thu, 23 Mar 2006 01:06:51 GMT https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939476#M14381 everest 2006-03-23T01:06:51Z https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939477#M14382 If you didn't try the usual stack limit adjustments:<BR />/link /stack:nnnnnnnnn (and its relatives, for Windows, along with /3GB boot parameter for XP-32)<BR />info ulimit (linux)<BR />those should apply, but they would not fit your "strange" description.<BR />It looks like you could run into the shortage of address space under 32-bit XP-SP2 with everything set to default, but I hesitate to guess your OS. Thu, 23 Mar 2006 01:58:37 GMT https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939477#M14382 TimP 2006-03-23T01:58:37Z https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939478#M14383 <DIV>Hi,</DIV><DIV></DIV><DIV>I am using Linux (SLES 2.6.5-7.151-smp). The machine I am using has following CPU</DIV><DIV></DIV><DIV>processor : 0<BR />vendor_id : GenuineIntel<BR />cpu family : 15<BR />model : 3<BR />model name : Intel Pentium 4 CPU 3.40GHz<BR />stepping : 4<BR />cpu MHz : 3393.886<BR />cache size : 1024 KB<BR />physical id : 0<BR />siblings : 2<BR />fdiv_bug : no<BR />hlt_bug : no<BR />f00f_bug : no<BR />coma_bug : no<BR />fpu : yes<BR />fpu_exception : yes<BR />cpuid level : 5<BR />wp : yes<BR />flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni<BR />monitor ds_cpl cid<BR />bogomips : 6701.05<BR /></DIV><DIV>and my "limit" scenario is as follows</DIV><DIV>cputime unlimited<BR />filesize unlimited<BR />datasize unlimited<BR />stacksize 8192 kbytes<BR />coredumpsize 0 kbytes<BR />memoryuse unlimited<BR />vmemoryuse unlimited<BR />descriptors 1024<BR />memorylocked unlimited<BR />maxproc 32255<BR /></DIV> Wed, 29 Mar 2006 01:55:50 GMT https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-memory-limitation/m-p/939478#M14383 everest 2006-03-29T01:55:50Z