Skip to content

[Improvement] Think of a better way to store the pricing DB #32

Description

@Saaketh0

Currently, to get the token/server costs of a request, we have built a teensy SQLite DB that we query, but this DB is both static and kinda awkward. What are some ways we can structure this better, considering we just need to build it once, and update it rarely.

Possible Fixes:
Just store a hash map of the values - doesn't solve the problem but simpler
idk

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions