Skip to main content

Glossary

The vocabulary used consistently across the platform, the docs, and these courses.

A

Activity logThe record of actions taken inside an organization: who created a workspace, changed a role, or launched a cluster.
ActorA distributed object that holds state across many calls. Created by applying the distribute decorator to a class rather than a function.
AdministrationThe operational side of Eugo: managing members and roles, monitoring usage, and reviewing activity logs.
ARM NeoverseThe ARM server processor architecture Eugo’s compute nodes are built on, chosen for performance per watt on numeric workloads.
Automatic optimizationTransformations Eugo applies to your code as it runs: vectorization, GPU offloading, and low-level tuning, with no annotation from you.

B

C

D

#

E

F

G

H

I

J

Job schedulerThe queueing system on a traditional HPC cluster that decides when a submitted job runs. Eugo has no queue: you launch a cluster and dispatch work to it.

L

Long tailThe situation where most tasks finish quickly but one or two run much longer, so the whole run waits on them while workers sit idle.

M

MemberA user who belongs to an organization. What a member can do is governed by their assigned role.

N

NotebookA document interleaving code, output, and prose. The primary interface for writing Python in EugoIDE.

O

P

R

RoleThe permission level a member holds in an organization, determining what they can change rather than only what they can see.

S

T

U

UsageAccumulated compute consumed by an organization in a billing period, shown against plan limits on the dashboard.

V

VectorizationRewriting operations so a single instruction processes several data elements at once, using the processor’s wide registers.

W