Learn more about MATLAB Compiler

Reserving Memory for Deployed Applications with MATLAB Memory Shielding

On this page…
What Is MATLAB Memory Shielding and When Should You Use It? Requirements for Using MATLAB Memory Shielding Invoking MATLAB Memory Shielding for Your Deployed Application

What Is MATLAB Memory Shielding and When Should You Use It?

Occasionally you encounter problems ensuring that you have the memory needed to run deployed applications. These problems often occur when:

• Your data set is large

• You are trying to compensate for the memory limitations inherent in a 32-bit Windows system

• The computer available to you has limited resources

• Network resources are restrictive

Use MATLAB Memory Shielding to ensure that you obtain the maximum amount of contiguous memory to run your deployed application successfully.

MATLAB Memory Shielding provides the specified level of protection of the address space used by MATLAB. When you use this feature, it reserves the largest contiguous block of memory available for your application after startup.

Memory shielding works by ensuring that resources, such as DLLs, load into locations that will not fragment the address space of the system. The feature provides the specified amount of contiguous address space you specify, up to the maximum available on the system.

For example, on a 32-bit Windows system, MATLAB defaults to memory shielding for virtual addresses 0x50000000-0x70000000. At the point where your application runs, the shield lowers, allowing allocation of that virtual address space.

Note   This topic describes how to invoke the shielding function for deployed applications, not the MATLAB workspace. To learn more about invoking memory shielding for MATLAB workspaces, see the discussion of the start-up option matlab shieldOption in the MATLAB Function Reference Guide.

Back to Top

Requirements for Using MATLAB Memory Shielding

Before using MATLAB Memory Shielding for your deployed applications, verify that you meet the following requirements:

• Your deployed application is failing because it cannot find the proper amount of memory and not for another unrelated reason. As a best practice, let the operating system attempt to satisfy run-time memory requests, if possible. See What Is MATLAB Memory Shielding and When Should You Use It? for examples of cases where you can benefit by using MATLAB Memory Shielding

• Your application runs on a Windows® 32-bit system. While MATLAB Memory Shielding runs on 64-bit Windows® systems without failing, it has no effect on your application.

• You are running with a standalone application or Windows executable. MATLAB Memory Shielding does not work with shared libraries, .NET components or Java components.

• You have run the MCR Installer on your system to get the MATLAB Component Runtime (MCR). The memory shielding feature is installed with the MCR.

Back to Top

Invoking MATLAB Memory Shielding for Your Deployed Application

Invoke memory shielding by using either the command-line syntax or the GUI. Each approach has appropriate uses based on your specific memory reservation needs.

Using the Command Line

Use the command line if you want to invoke memory shielding only with the various shield_level values (not specific address ranges).

The base command-line syntax is:

MemShieldStarter [-help] [-gui] [-shield shield_level] fully-qualified_application_path [user-defined_application_arguments]

1. Run your application using the default level of memory shielding. Use the command:

   MemShieldStarter fully-qualified_application_path [user-defined_application_arguments]

2. If your application runs successfully, try the next highest shield level to guarantee more contiguous memory, if needed.

   • A higher level of protection does not always provide a larger size block and can occasionally cause start-up problems. Therefore, start with a lower level of protection and be conservative when raising the level of protection.

   • Use only memory shielding levels that guarantee a successful execution of your application. See the table MemShieldStarter Options for more details on which shield options to choose.

   • Contact your system administrator for further advice on successfully running your application.

3. If your application fails to start, disable memory shielding:

   1. To disable memory shielding after you have enabled it, run the following command:

      MemShieldStarter -shield none fully-qualified_application_path [user-defined_application_arguments]

   2. Contact your system administrator for further advice on successfully running your application.

MemShieldStarter Options

Option	Description
-help	Invokes help for MemShieldStarter
-gui	Starts the Windows graphical interface for MemShieldStarter.exe. See Using the GUI for more details.
-shieldshield_level	See Shield Level Options.
fully-qualified_application_path	The fully qualified path to your user application
user-defined_application_arguments	Arguments passed to your user application. MemShieldStarter.exe only passes user arguments. It does not alter them.

Shield Level Options.   shield_level options are as follows:

• none — This value completely disables memory shielding. Use this value if your application fails to start successfully with the default (-shield minimum) option.

• minimum — The option defaults to this setting. Minimum shielding protects the range 0x50000000 to 0x70000000 during startup until just before processing matlabrc. This value ensures at least approximately 500 MB of contiguous memory available up to this point.

  When experimenting with a shielding level. start with minimum. To use the default, do not specify a shield option upon startup. If your application fails to start successfully using minimum, use -shield none. If your application starts successfully with the default value for shield_level, try using the -shield medium option to guarantee more memory.

• medium — This value protects the same range as minimum, 0x50000000 to 0x70000000, but protects the range until just after startup processes matlabrc. It ensures that there is at least approximately 500 MB of contiguous memory up to this point. If MATLAB fails to start successfully with the -shield medium option, use the default option (-shield minimum). If MATLAB starts successfully with the -shield medium option and you want to try to ensure an even larger contiguous block after startup, try using the -shield maximum option.

• maximum — This value protects the maximum range, which can be up to approximately 1.5 GB, until just after startup processes matlabrc. The default memory shielding range for maximum covers 0x10000000 to 0x78000000. If MATLAB fails to start successfully with the -shield maximum option, use the -shield medium option.

  Note   The shielding range may vary in various locales. Contact your system administrator for further details.

Using the GUI

Use the graphical interface to invoke memory shielding for specific address ranges as well as with specific shield_level values.

1. To start the GUI, run the following at the system command prompt:

   MemShieldStarter.exe -gui

   The Memory Shielding Starter dialog box opens:

   

2. Enter the appropriate values as described in MemShieldStarter Options. Use the default Memory shielding level minimum.

   You can specify a specific address range in the Memory address range fields. Specifying a range override the default 0x50000000 through 0x70000000 address range values required for the shield_level minimum, for example.

3. Click Run.

4. If your application runs successfully, try the next highest shield level to guarantee more contiguous memory, if needed.

   • A higher level of protection does not always provide a larger size block and can occasionally cause startup problems. Therefore, start with a lower level of protection and use only what is necessary to guarantee a successful execution of your application.

   • See the table MemShieldStarter Options for more details on appropriate shield options for various situations.

Back to Top

Using MATLAB Compiler Generated DLLs in Windows Services

Compiler Commands

© 1984-2009- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS