Binary MEX files built on 64-bit platforms can handle 64-bit
mxArrays. These large data arrays can have up to
248-1 elements. The maximum number of elements a sparse
mxArray can have is 248-2.
Using the following instructions creates platform-independent binary MEX files as well.
Your system configuration can affect the performance of MATLAB®. The 64-bit processor requirement enables you to create the
mxArray and access data in it. However, the system memory, in
particular the size of RAM and virtual memory, determine the speed at which MATLAB processes the
mxArray. The more memory available, the
faster the processing.
The amount of RAM also limits the amount of data you can process at one time in MATLAB. For guidance on memory issues, see Strategies for Efficient Use of Memory. Memory management within source MEX files can have special considerations, as described in Memory Management.
The signatures of the API functions shown in the following table
to work with a 64-bit
mxArray. The variables you
use in your source code to call these functions must be the correct
mxArray Functions Using mwSize/mwIndex
1Fortran function only.
2C function only.
Functions in this API use the
shows memory requirements of large
mxArrays. To see the example,
open the file in MATLAB Editor.
This function requires one positive scalar numeric input, which it uses to create
a square matrix. It checks the size of the input to make sure that your system can
theoretically create a matrix of this size. If the input is valid, it displays the
size of the
mxArray in kilobytes.
Build this MEX file.
Run the MEX file.
Dimensions: 1024 x 1024 Size of array in kilobytes: 1024
If your system does not have enough memory to create the array, MATLAB displays an
Out of memory error.
You can experiment with this function to test the performance and limits of handling large arrays on your system.
When using the 64-bit API,
mwIndex are equivalent to
C/C++. This type is unsigned, unlike
int, which is the type used
in the 32-bit API. Be careful not to pass any negative values to functions that take
mwIndex arguments. Do not
int values to
mwIndex; the returned value cannot be predicted. Instead,
change your code to avoid using negative values.
If you develop programs that can run on both 32- and 64-bit architectures, pay
attention to the upper limit of values for
mwIndex. The 32-bit application reads these values and
assigns them to variables declared as
int in C/C++. Be careful to
avoid assigning a large
value to an
int or other variable that might be too small.