[mesa-users] RAM issues in sdb_test

[Bill Paxton]

Hmmmm ----- we're now into things I know nothing about.
let's see if there is anyone on mesa-users who can step in.
Any Ubuntu experts out there?

-B




On Jun 27, 2013, at 1:04 PM, sutirtha sengupta wrote:

> Hi Bill, 
> I should have also replied to you but see the forwarded message below regarding the output for ulimit -a as suggested by Josiah.
> Also here is the terminal output for the run I just made (using the sdb test suite) - had to do it by ssh since the computer freezes as soon as the data is loaded into RAM (see the attached htop screenshot status) :P
> 
> sutirtha at aibn160:/vol/aibn160/aibn160_1/sutirtha/codes/MESA/cemps/mesa-4904/star/test_suite/sdb$ ./rn
> DATE: 2013-06-27
> TIME: 21:57:27
>  saved initial &star_job inlist values: star_job_namelist.out
>                                          version_number        4936
>  read inlist_sdb
> load saved model sdb.mod
> 
>  reading OP cache file /vol/aibn160/aibn160_1/sutirtha/codes/MESA/cemps/mesa-4904/data/kap_data/op_mono_cach.bin
>  done reading OP cache file
>  set_initial_age   0.0000000000000000     
>  set_initial_dt   1000.0000000000000     
>  set_initial_model_number           0
>  change to basic_plus_fe56_ni58.net
>  number of species =          10
>  change_lnPgas_flag = T
>  net name basic_plus_fe56_ni58.net
>  do_element_diffusion T
>  lnPgas_flag = T
>                       use small_mtx_decsol bcyclic_dble          10         100
>  kappa_file_prefix OP
>  kappa_lowT_prefix lowT_fa05_gs98
>    eos_file_prefix mesa
>                                         OMP_NUM_THREADS           4
> 
> 
> __________________________________________________________________________________________________________________________________________________
> 
>        step    lg_Tcntr    Teff       lg_LH     lg_Lnuc     Mass       H_rich     H_cntr     N_cntr     Y_surf     X_avg     eta_cntr   pts  retry
>    lg_dt_yr    lg_Dcntr    lg_R       lg_L3a    lg_Lneu     lg_Mdot    H_poor     He_cntr    O_cntr     Z_surf     Y_avg     gam_cntr  iters bckup
>         age    lg_Pcntr    lg_L       lg_LZ     lg_Psurf    lg_Dsurf   He_poor    C_cntr     Ne_cntr    Z_cntr     Z_avg     v_div_cs     dt_limit
> __________________________________________________________________________________________________________________________________________________
> 
> log_dt 3.000   age 0.000E+00   model    1   iters  246   steps  246   retries    0   nzlo   12   nzhi  596   n  585   nz  631   diffusion_call_number    1
>           1   8.055024  2.793E+04  -7.533101   0.809822   0.462161   0.000117   0.000000   0.005494   0.317840   0.000220   0.493794    631      0
>    3.000000   4.352398  -0.861374   0.786628  -0.589184 -99.000000   0.462045   0.906993   0.004434   0.019101   0.931643   0.159352      3      0
>  1.0000E+03  20.244529   1.015151  -0.474140   4.507572  -8.088677   0.000000   0.070082   0.008758  9.301E-02  6.814E-02 -0.787E-09    varcontrol
> 
> save LOGS/profile1.data for model 1
> 
> 
> ---------- Forwarded message ----------
> From: sutirtha sengupta <sutirtha.sg86 at gmail.com>
> Date: Thu, Jun 27, 2013 at 7:17 PM
> Subject: Re: [mesa-users] RAM issues in sdb_test
> To: Josiah Schwab <jwschwab at berkeley.edu>
> 
> 
> I got the following output from ulimit -a:
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 62882
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 65535
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 62882
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
> 
> Sutirtha.
> 
> 
> 
> On Thu, Jun 27, 2013 at 7:04 PM, Josiah Schwab <jwschwab at berkeley.edu> wrote:
> > I hope you are willing to do some digging on this one since there's nothing obvious for a quick fix.
> 
> It might be useful to see the output of ulimit -a and see the value of max memory size or related parameters.
> 
> Josiah
> 
> 
> <htop_aibn160.png>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20130627/d0701941/attachment.html>