Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/gptscript runner #295

Merged
merged 107 commits into from
May 19, 2024
Merged

Feature/gptscript runner #295

merged 107 commits into from
May 19, 2024

Conversation

rusenask
Copy link
Contributor

@rusenask rusenask commented May 14, 2024

Adding a dedicated script runner, currently only in the docker-compose.dev.yaml:

  gptscript_runner:    
    build:
      context: .
      dockerfile: Dockerfile.gptscript        
    restart: always
    environment:
      - OPENAI_API_KEY=${OPENAI_API_KEY:-}
      - API_HOST=http://api:80
      - API_TOKEN=${RUNNER_TOKEN-oh-hallo-insecure-token}
      - CONCURRENCY=20 # number of tasks to run concurrently
      - MAX_TASKS=1  # max number of tasks to run before exiting. Set to 0 to run forever

Goals:

  • Concurrency
  • Max tasks before restart
  • Decent throughput so it would be possible to have an APIs that use gptscript under the hood

Next steps

While a one-shot runner works for low req/s callers, multiple runners should be used. There will be some additional work done on the pubsub package to prevent message from being sent to the runner that's about to shutdown so we don't have to retry.

@rusenask rusenask changed the title [WIP] Feature/gptscript runner Feature/gptscript runner May 19, 2024
@rusenask rusenask marked this pull request as ready for review May 19, 2024 12:57
@rusenask rusenask merged commit db3278e into main May 19, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant