slaily

3 ms·

1. 1.▲
   by slaily 1y ago

   When your program does heavy concurrent writing and opens/closes connections for each write, most of them will fail with SQLITE_BUSY or SQLITE_LOCKED errors. This situation can be managed with a pool of small (5 connections or less) to
2. 2.▲
   SQLite async connection pool for high-performance(github.com)

   197 points by slaily 1y ago|84 comments
3. 3.▲
   by slaily 1y ago

   If you’re building Python async apps (FastAPI, background jobs, etc.) with SQLite, you’ll eventually hit two issues - Opening/closing connections is fast, but not free—overhead adds up under load - SQLite writes are globally locked aio
4. 4.▲
   Show HN: Better prompt(prompteval.co)

   2 points by slaily 2y ago|0 comments
5. 5.▲
   by slaily 2y ago

   Here's the routine I've developed: 1. Pre-work ritual: 5 minutes of breathing exercises to clear my mind. 2. Environment setup: Focus music (playlist), all notifications off. 3. Session structure: - 90 minute deep work block
6. 6.▲
   Show HN: Free deep work app with no ads, no paywalls, and no tracking(tikie.co)

   1 points by slaily 2y ago|1 comments