evazion f6abf39ebc search: try to optimize slow searches.
Try to optimize certain types of common slow searches:

* Searches for mutually-exclusive tags (e.g. `1girl multiple_girls`,
  `touhou solo -1girl -1boy`)
* Relatively large tags that are heavily skewed towards old posts
  (e.g. lucky_star, haruhi_suzumiya_no_yuuutsu, inazuma_eleven_(series),
  imageboard_desourced).
* Mid-sized tags in the <30k post range that Postgres thinks are
  big enough for a post id index scan, but a tag index scan is faster.

The general pattern is Postgres not using the tag index because it
thinks scanning down the post id index would be faster, but it's
actually much slower because it degrades to a full table scan. This
usually happens when Postgres thinks a tag is larger or more common than
it really is. Here we try to force Postgres into using the tag index
when we know the search is small.

One case that is still slow is `2girls -multiple_girls`. This returns no
results, but we can't know that without searching all of `2girls`. The
general case is searching for `A -B` where A is a subset of B and A and B
are both large tags.

Hopefully fixes #581, #654, #743, #1020, #1039, #1421, #2207, #4070,
 #4337, #4896, and various other issues raised over the years regarding
slow searches.
2021-10-12 02:30:30 -05:00
2019-10-28 21:37:34 -05:00
2021-03-01 00:39:47 -06:00
2021-09-24 08:40:33 -05:00
2017-10-09 14:45:23 -07:00
2021-09-22 05:36:22 -05:00
2021-09-27 19:17:04 -05:00
2020-06-21 15:15:47 -05:00
2021-09-24 08:40:33 -05:00
2021-09-14 21:40:39 -05:00
2021-09-21 02:56:23 -05:00
2020-06-27 13:03:04 -05:00
2021-06-17 04:10:26 -05:00
2019-10-02 01:52:24 -05:00
2021-03-01 00:39:47 -06:00
2021-03-31 21:32:01 -05:00
2021-09-20 06:17:57 -05:00
2020-06-07 17:14:41 -05:00
2021-09-27 10:43:29 -05:00
2021-01-28 16:20:56 +09:00
2021-09-15 06:23:20 -05:00
2019-12-22 21:23:37 -06:00
2021-09-24 08:40:33 -05:00
2021-09-30 08:24:51 -05:00

codecov Discord

Quickstart

Run this to start a basic Danbooru instance:

curl -sSL https://raw.githubusercontent.com/danbooru/danbooru/master/bin/danbooru | sh

This will install Docker Compose and use it to start Danbooru. When it's done, Danbooru will be running at http://localhost:3000.

Alternatively, if you already have Docker Compose installed, you can just do:

wget https://raw.githubusercontent.com/danbooru/danbooru/master/docker-compose.yaml
docker-compose up

Manual Installation

Follow the INSTALL.debian script to install Danbooru.

The INSTALL.debian script is written for Debian, but can be adapted for other distributions. Danbooru has been successfully installed on Debian, Ubuntu, Fedora, Arch, and OS X. It is recommended that you use an Ubuntu-based system since Ubuntu is what is used in development and production.

See here for a guide on how set up Danbooru inside a virtual machine.

For best performance, you will need at least 256MB of RAM for PostgreSQL and Rails. The memory requirement will grow as your database gets bigger.

In production, Danbooru uses PostgreSQL 10.18, but any release later than this should work.

Troubleshooting

If your setup is not working, here are the steps I usually recommend to people:

  1. Test the database. Make sure you can connect to it using psql. Make sure the tables exist. If this fails, you need to work on correctly installing PostgreSQL, importing the initial schema, and running the migrations.

  2. Test the Rails database connection by using bin/rails console. Run Post.count to make sure Rails can connect to the database. If this fails, you need to make sure your Danbooru configuration files are correct.

  3. Test Nginx to make sure it's working correctly. You may need to debug your Nginx configuration file.

  4. Check all log files.

Services

Danboou depends on a couple of cloud services and several microservices to implement certain features.

Amazon Web Services

The following features require an Amazon AWS account:

  • Pool history
  • Post history

Google APIs

The following features require a Google Cloud account:

  • BigQuery database export

IQDB Service

IQDB integration is delegated to the IQDB service.

Archive Service

In order to access pool and post histories you will need to install and configure the Archives service.

Reportbooru Service

The following features are delegated to the Reportbooru service:

  • Post views
  • Missed searches report
  • Popular searches report

Recommender Service

Post recommendations require the Recommender service.

Description
No description provided
Readme 68 MiB
Languages
Ruby 78.3%
HTML 13.5%
JavaScript 3.5%
SCSS 2.5%
Nix 1.6%
Other 0.5%