πŸ“š
Docs - Float16
homeapp
  • πŸš€GETTING STARTED
    • Introduction
    • Account
      • Dashboard
      • Profile
      • Payment
      • Workspace
      • Service Quota
    • LLM as a service
      • Quick Start
        • Set the credentials
      • Supported Model
      • Limitation
      • API Reference
    • One Click Deploy
      • Quick Start
        • Instance Detail
        • Re-generate API Key
        • Terminate Instance
      • Features
        • OpenAI Compatible
        • Long context and Auto scheduler
        • Quantization
        • Context caching
      • Limitation
      • Validated model
      • Endpoint Specification
    • Serverless GPU
      • Quick Start
        • Mode
        • Task Status
        • App Features
          • Project Detail
      • Tutorials
        • Hello World
        • Install new library
        • Prepare model weight
        • S3 Copy output from remote
        • R2 Copy output from remote
        • Direct upload and download
        • Server mode
        • LLM Dynamic Batching
        • Train and Inference MNIST
        • Etc.
      • CLI References
      • ❓FAQ
    • Playground
      • FloatChat
      • FloatPrompt
      • Quantize by Float16
  • πŸ“šUse Case
    • Q&A Bot (RAG)
    • Text-to-SQL
    • OpenAI with Rate Limit
    • OpenAI with Guardrail
    • Multiple Agents
    • Q&A Chatbots (RAG + Agents)
  • ✳️Journey
    • ✨The Beginner's LLM Development Journey
    • πŸ“–Glossary
      • [English Version] LLM Glossary
      • [ΰΈ ΰΈ²ΰΈ©ΰΈ²ΰΉ„ΰΈ—ΰΈ’] LLM Glossary
    • 🧠How to install node
  • Prompting
    • πŸ“šVariable
    • ⛓️Condition
    • πŸ”¨Demonstration
    • βŒ›Loop
    • πŸ“™Formatting
    • 🐣Chat
    • πŸ”ŽTechnical term (Retrieve)
  • Privacy Policy
  • Terms & Conditions
Powered by GitBook
On this page
  1. GETTING STARTED
  2. Serverless GPU

FAQ

Frequently Ask Question about Serverless GPU

PreviousCLI ReferencesNextPlayground

Last updated 2 months ago

Why can't I create a new project?

In the beta version, users are limited to one active project at a time. If you need to create a new project, you must first delete your current project using the command:

float16 project delete
  • Once a project is deleted, it cannot be restored

  • All deployed endpoints will be automatically deleted when the project is removed

How can I find my project ID?

You can locate your project ID through several methods:

Using CLI:

  • Run float16 project list

  • Your current project ID will appear at the top of the table with "active" status

Checking float16.conf:

  • Look for the 'project_id' parameter in your float16.conf file

Why am I getting a "project ID not found" error?

This error occurs when the system cannot locate your project ID. Check the following:

  1. Verify that you have a float16.conf file in your current directory

    • If missing, run float16 init to create it

  2. Confirm that you have created a project

    • If not, use float16 project create to create one

    • The project ID will automatically update in your float16.conf file

  3. If you created the project in another path or folder

    • Locate the float16.conf file in the directory where you last used the project

    • Manually copy the project ID from that configuration file

    • Apply the copied project ID to your current working directory's configuration

  4. If you're still experiencing issues, contact our support team

Why am I getting "files not found" errors when running or deploying?

This error typically occurs when:

  • The file is actually missing

  • You're trying to access files in subfolders

You must be in the same directory as your target file when using run or deploy commands.

Why does my remote storage contain files I didn't copy?

The CLI automatically uploads certain files:

  • All .py files in your directory during run or deploy operations

  • Your requirements.txt file (if not empty) when you use float16 project start

When to use float16 project start ?

Imagine your project is like a car parked in a garage. The float16 project start command is essentially turning the key and warming up the engine. It's your go-to command when you want to breathe life into your project's environment.

Think of it as a wake-up call for your development container. After creating a new project or if you've been away for more than 24 hours, this command springs your environment back to action. It does two critical things: creates or reactivates your container and automatically installs all the libraries specified in your requirements.txt.

  • New project? Run float16 project start

  • Haven't coded in over a day? Use the command

PS. In deployment mode, you won't need thisβ€”the float16 deploy command handles container activation automatically.

Why am I not getting any response?

In the beta version, there is a computation time limit. If your computation exceeds this limit, you will receive a null response from the server.

Why am I getting "Endpoint is unavailable" response?

Your endpoint is currently inactive. When an endpoint is in an inactive state, it cannot process requests or return responses.

How to Verify:

  • Use float16 endpoint command to view current status

How to Resolve:

float16 endpoint start
What is the difference between On-Demand and Spot tasks?

On-Demand Task

An on-demand task runs for a maximum of 30 seconds without any interruptions. It supports three trigger types: manual, function, and server. These tasks can be executed in both development mode and production mode. Pricing is based on the on-demand rate.

Spot Task

A spot task runs in Spot Mode, which allows execution beyond 30 seconds but can be interrupted if an on-demand task requires resources. Once the on-demand task is completed, the spot task automatically resumes. Pricing follows the spot rate, which is typically lower than the on-demand rate.

πŸš€
❓