Skip to main content
Glama
ArcadeData

ArcadeDB Multi-Model DBMS

Official

profiler_start

Start capturing query execution data including execution times and plans in ArcadeDB. The profiler automatically stops after a configurable timeout or can be stopped manually to analyze performance.

Instructions

Start the query profiler to capture query execution data. The profiler records all queries with their execution times and plans. It auto-stops after the specified timeout (default 60 seconds). Use profiler_stop to stop early and get results, or profiler_status to check progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutSecondsNoRecording timeout in seconds. The profiler auto-stops after this duration. Default: 60.

Implementation Reference

  • The profilerStart function implementation sends a "profiler start [timeout]" command to the server via an AJAX POST request.
    function profilerStart() {
      var timeout = jQuery("#profilerTimeout").val() || "60";
      jQuery.ajax({
        type: "POST",
        url: "api/v1/server",
        data: JSON.stringify({ command: "profiler start " + timeout }),
        headers: { Authorization: globalCredentials },
        contentType: "application/json",
        success: function() {
          profilerStartTime = Date.now();
          profilerTimeoutMs = parseInt(timeout) * 1000;
          profilerSetRecordingUI(true);
          globalNotify("Profiler", "Recording started (auto-stop in " + timeout + "s)", "success");
        },
        error: function(jqXHR) { globalNotifyError(jqXHR.responseText); }
      });
    }

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArcadeData/arcade-db-multi-model-dbms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server