1. Using Graph Studio in Oracle Autonomous Database
  2. Manage the Compute Environment
  3. Manually Manage the Compute Environment

Manually Manage the Compute Environment

Although Graph Studio can automatically manage the attaching and detaching process of the compute environment in the background, you can also manually manage the environment.

The following lists a few situations which require manual intervention:
  • Increase (or decrease) the maximum amount of the graph server (PGX) memory available for analysis and optionally save the memory value as the default graph server (PGX) memory configuration.
  • Increase (or decrease) the maximum amount of memory available for notebook interpreters and optionally save the memory values as the default memory configurations for the interpreters.
  • Code in a notebook accidentally caused the environment to enter a bad state.
  • The environment ran out of memory.
To manually manage the environment:
  1. Click on your username on the top right drop-down menu of Graph Studio and then select Compute Environment.

    The Compute Environment slider appears as shown:


    Description of manually_manage_env.png follows
    Description of the illustration manually_manage_env.png

  2. Click Restart or Attach or Detach as it may apply.

    The following table describes all the supported manual options to manage the compute environment:

    Manual Options Description
    Detach the compute environment

    If the compute environment is currently attached, you can detach it by clicking the Stop button. This will cause the compute environment to enter the Detaching state.

    Attach the compute environment

    If the compute environment is currently detached, you can:

    1. Select the amount of Graph server memory you want to attach to the compute environment.

      It is important to note that currently Graph Studio does not allow allocation of more than 109 GB of memory for graph analysis per tenancy.

      In case you get one of the following error messages, although you selected less than 109 GB:
      • Not enough memory available
      • The number is too high
      then the cause could be one of the following:
      • Other Autonomous Databases in your tenancy currently being attached to the compute environment.
      • The sum of the memory given to the graph server and all the interpreters has exceeded the maximum memory allocation limit.
      If you require more memory, please contact Oracle Cloud Support.
    2. Click Interpreters to configure memory for the interpreters:
      • PGX interpreter memory

        Note that this memory configuration applies for the following interpreters as they all share the configured memory space:

        • Java (PGX) interpreter
        • PGQL (PGX) interpreter
        • Custom Algorithm (PGX) interpreter
      • Markdown interpreter memory
      • Python interpreter memory
      • Database interpreter memory

        Note that this memory configuration applies for the following interpreters as they all share the configured memory space:

        • SQL interpreter
        • PGQL (RDBMS) interpreter
        • SPARQL (RDF) interpreter
      • Conda interpreter memory
    3. Optionally, click Save preferences to save the values as the default memory settings.
    4. Click Create to attach to the compute environment.

      Note:

      The total amount of memory allocated to the compute environment is the sum of the memory given to the graph server and all the interpreters.
    Restart the compute environment You can detach and attach again in a single operation by clicking the Restart button. In this case, Graph Studio will attach to a compute environment with the same amount of memory as the current configuration for the graph server and the interpreters.
  3. Monitor the progress of any of the manual operations on the Jobs page.