base on Compute Node of Dria Knowledge Network. <p align="center"> <img src="https://raw.githubusercontent.com/firstbatchxyz/.github/refs/heads/master/branding/dria-logo-square.svg" alt="logo" width="168"> </p> <p align="center"> <h1 align="center"> Dria Compute Node </h1> <p align="center"> <i>Dria Compute Node serves the computation results within Dria Knowledge Network.</i> </p> </p> <p align="center"> <a href="https://opensource.org/license/apache-2-0" target="_blank"> <img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache%202.0-7CB9E8.svg"> </a> <a href="./.github/workflows/test.yml" target="_blank"> <img alt="Workflow: Tests" src="https://github.com/firstbatchxyz/dkn-compute-node/actions/workflows/tests.yml/badge.svg?branch=master"> </a> <a href="https://github.com/firstbatchxyz/dkn-compute-node/releases" target="_blank"> <img alt="Downloads" src="https://img.shields.io/github/downloads/firstbatchxyz/dkn-compute-node/total?logo=github&logoColor=%23F2FFEE&color=%2332C754"> </a> <a href="https://hub.docker.com/repository/docker/firstbatch/dkn-compute-node/general" target="_blank"> <img alt="Docker Version" src="https://img.shields.io/docker/v/firstbatch/dkn-compute-node?logo=Docker&label=image&color=2496ED&sort=semver"> </a> <a href="https://discord.gg/dria" target="_blank"> <img alt="Discord" src="https://dcbadge.vercel.app/api/server/dria?style=flat"> </a> </p> ## About Compute nodes can technically do any arbitrary task, from computing the square root of a given number to finding LLM outputs from a given prompt, or validating an LLM's output with respect to knowledge available on the web accessed via tools. - **Heartbeats**: Every few seconds, a heartbeat ping is published into the network, and every compute node responds with a digitally-signed pong message to indicate that they are alive, along with additional information such as which nodes they are running & how many tasks they have so far. - **Workflows**: Each task is given in the form of a [workflow](https://github.com/andthattoo/ollama-workflows). Every workflow defines an agentic behavior for the chosen LLM, all captured in a single JSON file, and can represent things ranging from simple LLM generations to iterative web searching & reasoning. ### Running a Node Use the [Dria Compute Launcher](https://github.com/firstbatchxyz/dkn-compute-launcher/) to run a compute node with many more features! ## Releases For _production_ images: - **Versioned**: With each release, a versioned image is deployed on Docker hub with the version tag `:vX.X.X`. - **Latest**: The latest production image is always under the `:latest` tag. For _development_ images: - **Master**: On each push to `master` branch, a new image is created with the tag `master-<commit>-<timestamp>`. - **Unstable**: The latest development image is always under the `:unstable` tag. You can see the list of deployed images on [Docker Hub](https://hub.docker.com/orgs/firstbatch/members). ## Development > If you have a feature that you would like to add with respect to its respective issue, or a bug fix, feel free to fork & create a PR! If you would like to run the node from source (which is really handy during development), you can use our shorthand scripts within the Makefile. You can see the available commands with: ```sh make help ``` You probably have already but in case you don't, you will need OpenSSL installed, see shorthand commands [here](https://github.com/sfackler/rust-openssl/issues/855#issuecomment-450057552). ```sh cargo run # specify custom .env file DKN_COMPUTE_ENV=./path/to/.env cargo run ``` If you have a valid `.env` file, you can run the latest Docker image via compose as well: ```sh docker compose up # Ollama without any GPUs docker compose --profile=ollama-cpu up # Ollama for NVIDIA gpus docker compose --profile=ollama-cuda up # Ollama for AMD gpus docker compose --profile=ollama-rocm up ``` Note that we are very dependent on Ollama packages, and it is important to check their versions if relevant: ```sh cat Cargo.lock | grep "https://github.com/andthattoo/ollama-workflows" cat Cargo.lock | grep "https://github.com/andthattoo/ollama-rs" ``` ### Testing You can the tests as follows: ```sh cargo test --workspace ``` We also have some benchmarking and profiling scripts, see [node performance](./docs/NODE_PERFORMANCE.md) for more details. ### Documentation You can view the entire crate-level documentation with: ```sh cargo doc --open --no-deps --document-private-items ``` ### Styling Lint and format with: ```sh cargo clippy --workspace cargo fmt -v ``` ### Profiling We have scripts to profile both CPU and Memory usage. A special build is created for profiling, via a custom `profiling` feature, such that the output inherits `release` mode but also has debug symbols. Furthermore, the profiling build will exit automatically after a certain time, as if CTRL+C has been pressed. This is needed by the memory profiling tool in particular. **CPU Profiling**: To create a [flamegraph](https://crates.io/crates/flamegraph) of the application, the command below will create a profiling build that inherits `release` mode, except with debug information: ```sh DKN_EXIT_TIMEOUT=120 cargo flamegraph --root --profile=profiling --bin dkn-compute ``` > [!NOTE] > > CPU profiling may require super-user access. **Memory Profiling**: To profile memory usage, we make use of [cargo-instruments](https://crates.io/crates/cargo-instruments): ```sh DKN_EXIT_TIMEOUT=120 cargo instruments --profile=profiling -t Allocations --bin dkn-compute ``` > [!TIP] > > You can adjust the profiling duration via the `DKN_EXIT_TIMEOUT` variable, which takes a number of seconds until termination. ## License This project is licensed under the [Apache License 2.0](https://opensource.org/license/Apache-2.0). ", Assign "at most 3 tags" to the expected json: {"id":"11539","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"