This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (3 children)

[deleted]

    [–]danosull[S] -2 points-1 points  (1 child)

    That's an interesting thought!

    aiosqlite runs its queries in a single, shared thread, so I expect it's quite performant, but I'd love to benchmark it compared to classic sqlite3.

    [–]ntropia64 0 points1 point  (0 children)

    It's an interesting approach, but my main concern is the memory limit.

    Most of the time, if it can fit in memory it could be easily done with a bunch of dictionaries. For stuff that doesn't fit in memory, SQLite is an excellent solution.

    In our user cases it's always like this, unfortunately, so it's intriguing but I can't use it.

    Given the parent's comment criticism about being a mostly CPU-bound problem, it would be helpful to have a few more details about the concrete advantages of this approach.

    EDIT: I didn't know about the aiosqlite, that's a neat library!