cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
The Discovery Summit 2025 Call for Content is open! Submit an abstract today to present at our premier analytics conference.
Get the free JMP Student Edition for qualified students and instructors at degree granting institutions.
Choose Language Hide Translation Bar
View Original Published Thread

Memory Issues after joining tables

AdditiveRange10
Level II

Hello All,

Very frustrating issue here. I perform a join of two tables. Both tables are small, about 9-10 rows and 40 columns. The join completes successfully with this code.

dt_join = dt1 << (With(dt2), Merge Same Name Columns, By Matching Columns(:col1 = :col1, :col2=:col2), Include Nonmatches(1,1), Preserve main table order(1));

If I run any code after that there are no issues. My total memory with just Chrome and File explorer and JMP is about 10%. However, if I try to do anything with the newly joined table the whole JMP app becomes unresponsive and has to be force closed.
Additionally, I had also tried (my ultimate goal) to join the joined table with one more table to yield a final joined table of 3 tables and when I attempt that I also get an unresponsive app and my memory usage goes to 99% and after some time I get a "unable to allocate memory message".
Here is my memory makeup under normal usage with JMP on but no actions taken on the joined table

AdditiveRange10_0-1734548240461.png


Any thoughts or possible solutions. This is incredible frustrating.

2 REPLIES 2
jthi
Super User


Re: Memory Issues after joining tables

Have you contacted JMP Support?

-Jarmo


Re: Memory Issues after joining tables

I think I see what the issue is. Each of the tables has 9-10 rows of images (from saving a table with graphs option). Working with each individual table by itself is quite alright but when joining them and now there is ~20 images I guess causes some memory issue. I removed the images and was able to do the three way join.

Either way, that seems like an action that should not completely hamstring a computer's memory especially with 64Gb RAM.
I might still contact support