Hi Kamil,
The bottleneck is Fit Model>Standard Least Squares implementation. Even with fit separately, it it is trying to put 1000 model results into a single report. And that is just the start of it. My guess is that it does this in linear time (one at a time), so one processor/thread is being used for generating the report. But I am only guessing.
I am not sure if you can specify how to use computer resources by JMP (except to turn multithreading off on a per platform basis in some of the platform dialogs). Many of the platforms are already multithreaded (I think Response Screening might be one of them). I am not sure about Fit Model>Standard Least Squares. I am also guessing that report generation is single threaded. But I would need a developer to let me know how this situation is working behind the scenes. Some functions cannot be multithreaded so max CPU capacity utilization might not be possible. Memory is similar. You can consume all of your memory just by clustering large data sets (1000s by 1000s in a two way hierarchical cluster). That is mainly to store the information for generating the graphical output.
I hope this gives some idea of what JMP does in the background. It tries to use what ever resources are available for that function/capability/platform, if it is possible.
By the way, we are continuing to enhance JMP Pro to accommodate wide data sets, such as yours. Fit Model>Mixed Models is one example where we have a red triangle option to dispose reports and only show tables. This makes it fast to fit a mixed model on 1000s of responses, but does not give a graphically based report.
Chris Kirchberg, M.S.2
Data Scientist, Life Sciences - Global Technical Enablement
JMP Statistical Discovery, LLC. - Denver, CO
Tel: +1-919-531-9927 ▪ Mobile: +1-303-378-7419 ▪ E-mail: chris.kirchberg@jmp.com
www.jmp.com