What 200 Concurrent Users Taught Me About SQLite Performance
Testing SQLite performance under 200 concurrent users revealed that bcrypt password verification, not the database, was the primary bottleneck. The solution involved offloading bcrypt work to separate, stateless worker services called Verifico. This architecture improved response times significantly while maintaining SQLite as the single database instance.
- ▪Autentico is a self-contained OAuth 2.0 and OpenID Connect provider using Go and SQLite.
- ▪Profiling showed that bcrypt password verification consumed 90% of CPU time, overshadowing SQLite performance.
- ▪Verifico was developed to offload bcrypt operations to remote workers, improving performance without scaling the entire application.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1225296) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Eugene Yakhnenko Posted on Apr 28 What 200 Concurrent Users Taught Me About SQLite Performance #sqlite #go #idp #performance I was about to release Autentico 2.0. The feature work was done, tests were passing, docs were updated. Before tagging the release I figured I'd spend some time on performance. Run some stress tests, see where things stand, maybe squeeze out some easy wins.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
