Code: Select all
Resolution 73997 Problem Summary: Performance issues working with large tables in SPSS 16.0 Problem Description: I am using SPSS 16.0. I produce output which can contain somewhat large tables. In previous versions of SPSS, the job runs to completion quickly (~15 seconds or less). On the same system with SPSS 16.0.0, this job takes a long time or never completes. The application may go gray and unresponsive. If the output generates, I have similar trouble editing, copying/pasting, exporting or printing the larger tables. For instance, it may take several seconds to copy the table or I am unable to print. Is there any way I can improve this behavior? Resolution Summary: The following workaround may help in this situation. Resolution Description: If you are running out of memory performing any operations with large tables or if your jobs are taking a long time to run, we recommend temporarily adjusting the Maximum Java Heap Size for the client system. On Linux and Windows, this heap can be adjusted upwards by creating a system environment variable, called ‘SPSSClientMaxHeapLevel’, on each SPSS client. This variable can be set to values 1, 2, or 3 where 1 = 512MB 2 = 768MB and 3 = 1024. 1 is the default value. E.g., Variable: SPSSClientMaxHeapLevel Value: 2 For Macintosh, the info.plist file needs to be edited. Info.plist, found in /Applications/SPSSInc/SPSS16/SPSS16.0.app/Contents/Info.plist is an XML file which contains the setting. If you wish to change the max heap value, you need to do the following: 1. In Terminal, type: $ cd /Applications/SPSSInc/SPSS16/SPSS16.0.app/Contents 2. Create a copy of the Info.plist file for safekeeping: $ cp Info.plist Info.plist.keep 3. Edit the Info.plist file. For instance, If you want to increase the max heap size to 768MB, you'd change: -Xmx512M to -Xmx768M $ vi Info.plist (search for "-Xmx512M", make the change in vi, then save Info.plist) Please note: The drawback of setting Maximum Java Heap Size too high is that it will take available memory away from the backend in single-seat mode, potentially limiting other procedures that can be run (if they require a lot of RAM) and possibly introducing video display problems.
Users browsing this forum: No registered users and 1 guest