| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Just use it for providing substitutes.
|
| | |
|
| |
|
|
| |
Mostly to constrain the build server event handlers.
|
| | |
|
| |
|
|
| |
As it's been broken for a long time now, there are too many rows to count.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Since the Guix daemon doesn't export these metrics, instrument it here.
|
| |
|
|
| |
As I've got no idea why the resource pools sometimes stop working.
|
| |
|
|
| |
As that makes debugging problems harder.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Now that squee cooperates with suspendable ports, this is unnecessary. Use a
connection pool to still support running queries in parallel using multiple
connections.
|
| |
|
|
| |
As this will help identify when the service restarts.
|
| |
|
|
|
|
|
|
| |
In to two thread pools, a default one, and one reserved for essential
functionality.
There are some pages that use slow queries, so this should help stop those
pages block other operations.
|
| |
|
|
|
|
|
|
|
| |
Newer versions of Guile Fibers will now use chunked encoding when a procedure
is used (and no content length is set). This is good, but not always what is
wanted, and there's also an issue with the port encoding.
This commit switches to responding with a string/bytevector when more
appropriate, plus explicitly setting the port encoding where that's needed.
|
| |
|
|
|
| |
This will allow for instrumenting low level database functionality, before
anything starts using the database.
|
| | |
|
| |
|
|
|
| |
As the guix-data-service process seems to be using excessive amounts of
memory, and this will be useful to track it.
|
| |
|
|
| |
As this is a little clearer.
|
| |
|
|
|
|
|
|
|
| |
The server part of the guix-data-service doesn't work great as a guix service,
since it often fails to start if the migrations take any time at all.
To address this, start the server before running the migrations, and serve the
pages that work without the database, plus a general 503 response. Once the
migrations have completed, switch to the normal behaviour.
|
| |
|
|
|
| |
This caused a problem viewing this derivation
/gnu/store/65r4488732qy6ilrh1ryb8xwmip1qnir-tklib-0.6.tar.gz?uuid=tklib-0-6.drv
|
| |
|
|
|
|
| |
From the HTML and JSON responses, since this data isn't very useful, and the
query to collect the small amount which is displayed is very slow. This could
return at some point, but in a proper paginated form which isn't slow.
|
| |
|
|
|
|
| |
This might be useful for working out when a non-master branch contains a newer
version of a package, or someone has sent in a patch for a newer version
already.
|
| |
|
|
| |
Rather than just completed or not.
|
| | |
|
| |
|
|
| |
As this will make it easier to tell where space is going.
|
| |
|
|
| |
As these were causing errors because they were nested in letpar&.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, a connection was passed through the code handling the
request. When queries were performed, this could block the thread though,
potentially leaving the server unable to serve other requests.
Instead, this now runs queries in a pool of threads. This should remove the
possibility of blocking the threads used by the web server, and in doing so,
some of the queries have been parallelised.
I''m still not sure about the naming and syntax, but I think the functionality
is a sort of step forward.
|
| |
|
|
|
|
|
| |
This was good in that it avoided having to deal with long running connections,
but it probably takes some time to open the connection, and these changes are
a step towards offloading the PostgreSQL queries to other threads, so they
don't block the threads for fibers.
|
| |
|
|
| |
Hopefully this'll help track database things better.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The database size is growing, but it's hard to know what parts are growing the
fastest. These metrics will hopefully help with understanding that.
|
| |
|
|
| |
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
| |
|
|
| |
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
| | |
|
| |
|
|
|
| |
This will help stop queries running for an unnecessarily long time, longer
than NGinx will wait for example.
|
| |
|
|
| |
Render some HTML rather than the plain response.
|
| |
|
|
|
| |
Adjust the previously unused error page code, and start to use it. Only show
the error if configured to do so, to avoid leaking secret information.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
If the nar file is available.
|
| | |
|