unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass)
Date: Fri, 17 May 2019 10:26:24 +0200	[thread overview]
Message-ID: <CAE4v=phgpfHSuAQwTp0ZoB_JYokEss9thdOLeROGmaJd=7cLGw@mail.gmail.com> (raw)
In-Reply-To: <87imuabhsw.fsf@roquette.mug.biscuolo.net>

[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]

Hello,

Giovanni Biscuolo <g@xelera.eu> ezt írta (időpont: 2019. máj. 16., Cs,
16:23):

> Hello Björn,
>
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:
>
> [...]
>
> >> 2) Cuirass
> >
> > On Guix days, we discussed the idea of using Postgresql as a backend.
>
> Please do you remember the rationale behind this idea?
>
>
This was just an idea to test if we can make the database scalability
problem we
currently have solved.


> What is the issue with using sqlite?
>

Currently the database response times on sqlite are not acceptable.
Any suggestions to overcome this would be appreciated.


> Why a client/server approach vs an embedded database?
>
> I don't have much experience with web applications backed by sqlite, but
> AFAIU sqlite is sometime "misunderstood"
>
> Some interesting arguments from sqlite developer:
> https://sqlite.org/whentouse.html#website
> --8<---------------cut here---------------start------------->8---
>
> Dynamic content uses about 200 SQL statements per webpage. This setup
> runs on a single VM that shares a physical server with 23 others and yet
> still keeps the load average below 0.1 most of the time.
>
> --8<---------------cut here---------------end--------------->8---
>
> https://sqlite.org/np1queryprob.html
> --8<---------------cut here---------------start------------->8---
>
> 200 SQL statements per webpage is excessive for client/server database
> engines like MySQL, PostgreSQL, or SQL Server.
>
> But with SQLite, 200 or more SQL statement per webpage is not a problem.
>
> SQLite can also do large and complex queries efficiently, just like
> client/server databases. But SQLite can do many smaller queries
> efficiently too. Application developers can use whichever technique
> works best for the task at hand.
>
> [...]
>
> N+1 Queries Are Not A Problem With SQLite
>
> --8<---------------cut here---------------end--------------->8---
>
> [...]
>
> Thanks! Gio'
>
> --
> Giovanni Biscuolo
>
> Xelera IT Infrastructures
>
Best regards,
g_bor

[-- Attachment #2: Type: text/html, Size: 3213 bytes --]

  reply	other threads:[~2019-05-17  8:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 21:45 Hackathon: Mumi and Cuirass Ricardo Wurmus
2019-05-04  7:19 ` Christopher Baines
2019-05-06 20:55 ` Björn Höfling
2019-05-06 22:10   ` Christopher Baines
2019-05-07  5:19   ` Ricardo Wurmus
2019-05-16 14:22   ` postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass) Giovanni Biscuolo
2019-05-17  8:26     ` Gábor Boskovits [this message]
2019-05-17 10:42       ` Aljosha Papsch
2019-05-17 20:29         ` Ricardo Wurmus
2019-05-17 12:58       ` Ricardo Wurmus
2019-05-21 10:19         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=phgpfHSuAQwTp0ZoB_JYokEss9thdOLeROGmaJd=7cLGw@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).