Quad Core 4MB and Code Aster Memory Error
- JMB
- Topic Author
- Offline
- Elite Member
-
Less
More
- Posts: 166
- Thank you received: 0
16 years 9 months ago #2173
by JMB
Quad Core 4MB and Code Aster Memory Error was created by JMB
Hello All,
I am running into a Code Aster memory error:
!
!
! <EXCEPTION> <JEVEUX_32>
! Erreur allocation de segment de m&#65533;moire de longueur 105136605 (entiers). !
! M&#65533;moire allou&#65533;e insuffisante. Fermeture des bases (glob.*) sur erreur !
! Il faut relancer le calcul en augmentant la limite m&#65533;moire. ! !
!
I am using CAELinux 2008.1 on an Intel Quad Core PC with 4GB of memory. The model has:
NOMBRE DE NOEUDS 667433
NOMBRE DE MAILLES 534747
SEG3 4432
TRIA6 133334
TETRA10 396981
NOMBRE DE GROUPES DE MAILLES 3
Fixed 4565
Symm_YZ 2494
Pressure 3373
This is a half model, since the full model would have been about 800K tetrahedral elements.
A few puzzling observations:
I am not able to make ASTK use more than 2048MB even though I have 4GB on the PC. I thought CAELinux was capable of supporting upto 4GB!
If I specify more than 2048MB, Code-Aster stops after an error complaining that only 2048MB can be used. Why?
Can Code-Aster not use the SWAP area I have created (10+GB) as additional memory space?
Is it possible to solve problems that are a few hundred thousand elements on such a PC?
Can anybody advice urgently please?
Thank you.
JMB
I am running into a Code Aster memory error:
!
!
! <EXCEPTION> <JEVEUX_32>
! Erreur allocation de segment de m&#65533;moire de longueur 105136605 (entiers). !
! M&#65533;moire allou&#65533;e insuffisante. Fermeture des bases (glob.*) sur erreur !
! Il faut relancer le calcul en augmentant la limite m&#65533;moire. ! !
!
I am using CAELinux 2008.1 on an Intel Quad Core PC with 4GB of memory. The model has:
NOMBRE DE NOEUDS 667433
NOMBRE DE MAILLES 534747
SEG3 4432
TRIA6 133334
TETRA10 396981
NOMBRE DE GROUPES DE MAILLES 3
Fixed 4565
Symm_YZ 2494
Pressure 3373
This is a half model, since the full model would have been about 800K tetrahedral elements.
A few puzzling observations:
I am not able to make ASTK use more than 2048MB even though I have 4GB on the PC. I thought CAELinux was capable of supporting upto 4GB!
If I specify more than 2048MB, Code-Aster stops after an error complaining that only 2048MB can be used. Why?
Can Code-Aster not use the SWAP area I have created (10+GB) as additional memory space?
Is it possible to solve problems that are a few hundred thousand elements on such a PC?
Can anybody advice urgently please?
Thank you.
JMB
- JMB
- Topic Author
- Offline
- Elite Member
-
Less
More
- Posts: 166
- Thank you received: 0
16 years 9 months ago #2174
by JMB
Replied by JMB on topic Re:Quad Core 4MB and Code Aster Memory Error
Hello,
According to this website:
"CAELinux 2008 is based on the PCLinuxOs 2007 distribution with the latest updates and should support the most recent hardwares / chipset for a much better compatibility and ease of use. It now comes with a newer kernel in version 2.6.22.17 with support for up to 4Gb Ram and 4 CPUs."
In reading the Code-Aster forums, I realize that CAELinux is compiled under a 32bit OS. Is a 64 bit version of CAELinux available?
Also I noticed that the Code_Aster *.mess file shows MPI: 1 CPU. Any reason why multi-CPU support was not compiled into Code-Aster?
Regards,
JMB<br /><br />Post edited by: JMB, at: 2008/08/03 23:32
According to this website:
"CAELinux 2008 is based on the PCLinuxOs 2007 distribution with the latest updates and should support the most recent hardwares / chipset for a much better compatibility and ease of use. It now comes with a newer kernel in version 2.6.22.17 with support for up to 4Gb Ram and 4 CPUs."
In reading the Code-Aster forums, I realize that CAELinux is compiled under a 32bit OS. Is a 64 bit version of CAELinux available?
Also I noticed that the Code_Aster *.mess file shows MPI: 1 CPU. Any reason why multi-CPU support was not compiled into Code-Aster?
Regards,
JMB<br /><br />Post edited by: JMB, at: 2008/08/03 23:32
Moderators: catux
Time to create page: 0.112 seconds