Hi all. With all apologies, I may be doing insufficient homework to ask here while I'm digging in to my support options at my University direct from Stata, but I'm hoping something jumps out as obvious here.
We have a high-profile user on a Redhat 7.4 64-bit VM, running Stata MP 15.1, with 8 CPU cores, 96GB physical RAM, and 16GB swap. He's been using this machine for similar work for almost a year without issue, but when he runs the code below on a 8.4GB dataset, the job visibly uses all physical RAM, then all available swap, then kills itself before completion.
I'm not a Stata user, but I am his support on this. Is there anything that's obviously wrong or any troubleshooting/resolution you might recommend?
His code:
We have a high-profile user on a Redhat 7.4 64-bit VM, running Stata MP 15.1, with 8 CPU cores, 96GB physical RAM, and 16GB swap. He's been using this machine for similar work for almost a year without issue, but when he runs the code below on a 8.4GB dataset, the job visibly uses all physical RAM, then all available swap, then kills itself before completion.
I'm not a Stata user, but I am his support on this. Is there anything that's obviously wrong or any troubleshooting/resolution you might recommend?
His code:
Code:
use /srv/scratch/salience/tmp, clear gen date=datadate ********************************* sort permco permno date merge 1:1 permco permno date using /srv/scratch/salience/crsp_daily_adjust, keepusing(permco permno date shrout cfacpr cfacshr shrcd exchc) sorted save /srv/scratch/salience/tmp2, replace
Comment