Movatterモバイル変換

mle.memory_max

Determines the maximum amount of memory to allocate to the MLE component. This variable is dynamic, but can be set only when the component is inactive; you can determine whether this is the case by checking the value of themle_status system status variable.

When increasing the value for this variable, you should be bear in mid that you must allow sufficient memory for other uses by the MySQL server such as buffer pools, connection memory, join buffers, and so on. In addition, there must be enough memory to allow system processes to operate correctly.

For more information about memory usage by the MLE component, seeSection 7.5.7.3, “MLE Component Memory and Thread Usage”.

mle_languages_supported

Lists the languages supported by the MLE component. In MySQL 9.1, this is alwaysJavaScript.

Available only if the MLE component is installed. SeeSection 7.5.7.2, “MLE Component Status and Session Information”, for more information.

mle_heap_status

Current status of the heap used by the MLE component. The value is one of:Not Allocated,Allocated, orGarbage Collection. The heap is allocated only if the MLE component is active (that is, ifmle_status is equal toActive).

Available only if the MLE component is installed. SeeSection 7.5.7.3, “MLE Component Memory and Thread Usage”, for more information.

mle_memory_used

Percentage of allocated memory used by the MLE component, rounded up to the nearest whole number.

Available only if the MLE component is installed. SeeSection 7.5.7.3, “MLE Component Memory and Thread Usage”, for more information.

mle_oom_errors

The total number of out-of-memory errors thrown by MLE stored programs, across all sessions.

Available only if the MLE component is installed. SeeSection 7.5.7.3, “MLE Component Memory and Thread Usage”, for more information.

mle_session_resets

The number of times MLE sessions have been cleared using themle_session_reset() function.

Available only if the MLE component is installed. SeeSection 7.5.7.2, “MLE Component Status and Session Information”, for more information.

mle_sessions

Current number of active MLE sessions. An MLE session is created within a given MySQL user session once the MySQL user creates or executes a JavaScript stored program. It is dropped when the MySQL user callsmle_session_reset(), or when the MySQL session ends.

If the MySQL user callsmle_session_reset(), then later creates or executes a JavaScript stored program within the same MySQL user session, a new MLE session is created. There can be at most one MLE session per MySQL session.

Available only if the MLE component is installed. SeeSection 7.5.7.2, “MLE Component Status and Session Information”, for more information.

mle_sessions_max

Maximum number of MLE sessions active at any one time since the MLE component became active.

Available only if the MLE component is installed. SeeSection 7.5.7.2, “MLE Component Status and Session Information”, for more information.

mle_status

Current status of the MLE component. The value is one of:Initializing,Inactive,Active, orPending Shutdown.

Available only if the MLE component is installed. SeeSection 7.5.7.2, “MLE Component Status and Session Information”, for more information.

mle_stored_functions

This is the number of MLE stored functions currently cached across all sessions.

Available only if the MLE component is installed. SeeSection 7.5.7.4, “MLE Component Stored Program Usage”, for more information.

mle_stored_procedures

The number of MLE stored procedures currently cached across all sessions.

Available only if the MLE component is installed. SeeSection 7.5.7.4, “MLE Component Stored Program Usage”, for more information.

mle_stored_programs

Returns the number of stored programs (stored procedures and stored functions) currently cached across all sessions. An MLE stored program is cached as soon it is executed for the first time, in each session in which it was executed. It is dropped from its session's cache when any of the following happens:

If the same stored program is executed again after being dropped from the cache, it is cached again as usual.

Available only if the MLE component is installed. SeeSection 7.5.7.4, “MLE Component Stored Program Usage”, for more information.

mle_stored_program_bytes_max

The size of the largest MLE stored program, in bytes. This value is equal to the size of the stored program's source text, expressed in bytes.

Available only if the MLE component is installed. SeeSection 7.5.7.4, “MLE Component Stored Program Usage”, for more information.

mle_stored_program_sql_max

The maximum number of SQL statements executed by any MLE stored program.

Available only if the MLE component is installed. SeeSection 7.5.7.4, “MLE Component Stored Program Usage”, for more information.

mle_threads

Returns the current number of physical threads attached to GraalVM. A physical thread, provided by the MySQL server's thread manager, is attached to GraalVM whenever it starts executing an operation inside GraalVM. Such operations include heap creation, code parsing, code execution, arguments conversion, memory usage queries, and deinitialization of stored programs. A thread is detached from GraalVM after it exits if the number of threads already attached exceeds the number of megabytes of heap allocated to Graal. The number of attached physical threads cannot exceed 1.5 times the number of megabytes of allocated Graal heap.

Available only if the MLE component is installed. SeeSection 7.5.7.3, “MLE Component Memory and Thread Usage”, for more information.

mle_threads_max

The maximum number of MLE threads active at any given time, since the MLE component last became active.

Available only if the MLE component is installed. SeeSection 7.5.7.3, “MLE Component Memory and Thread Usage”, for more information.