Inferix Decentralized GPU
  • Overview
  • Tokenomics
  • Introduction
    • Rendering network using crowdsourced GPU
    • Rendering verification problem
  • Decentralized visual computing
    • Client Apps plugin
    • Client API and SDK
    • Manager node
    • Worker node
    • Decentralized storage
      • Data categories
      • Multi-level 3D polygon data
      • Polygon digester
      • Decentralized storage
      • Decentralized cache
    • Data security with FHE and TEE
      • Verifier data security enhancement with FHE
      • Worker and Manager data security enhancement with FHE
    • Decentralized federated AI
      • Federated learning with TensorOpera
      • Meta LLaMA
      • Stable Diffusion
      • Other AI models
      • Inferix AI
  • Inferix Testnet 1
    • Inferix GPU Solutions
    • Adding GPUs to the Network
    • Renting GPU Devices
    • GPU Staking
  • Future development
    • PoR and NFT minting for graphics creative assets
    • ZKP and PoR communication
    • Inferix RemotePC
    • Rendering professional network
  • Terms of Service
    • Privacy Policy
    • Airdrop Terms of Service
Powered by GitBook
On this page
  1. Decentralized visual computing
  2. Decentralized storage

Multi-level 3D polygon data

In the stored data on Inferix, aside from images and videos, the geometry data of 3D models consumes the most storage space. Each time a render is performed, the Worker Node must download this data locally so that the render engines can execute the task. This process can consume significant bandwidth and time. To save bandwidth and reduce download times, 3D models are converted into two levels of detail, known as high-poly and low-poly, and are pre-stored on the Inferix network. The existence of multiple levels of 3D data is referred to as multi-level 3D polygon data.

PreviousData categoriesNextPolygon digester

Last updated 4 months ago