You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,18 @@ A driver for [Queues]. Uses [Fluent] to store job metadata in an SQL database.
9
9
10
10
This package makes use of the `SKIP LOCKED` feature supported by some of the major database engines (most notably [PostgresSQL][postgres-skip-locked] and [MySQL][mysql-skip-locked]) when available to make a best-effort guarantee that a task or job won't be picked by multiple workers.
11
11
12
-
This package should be compatible with:
12
+
This package should be compatible with any SQL database supported by the various Fluent drivers. It is specifically known to work with:
13
13
14
14
- PostgreSQL 11.0+
15
-
- MySQL 8.0+
15
+
- MySQL 5.7+
16
16
- MariaDB 10.5+
17
+
- SQLite
17
18
18
-
> [!NOTE]
19
+
> [!WARNING]
19
20
> Although SQLite can be used with this package, SQLite has no support for advanced locking. It is not likely to function correctly with more than one or two queue workers.
By default, the Vapor Queues system starts 2 workers per available CPU core, with each worker would polling the database once per second. On a 4-core system, this would results in 8 workers querying the database every second. Most configurations do not need this many workers.
84
+
By default, the Vapor Queues system starts 2 workers per available CPU core, with each worker would polling the database once per second. On a 4-core system, this would results in 8 workers querying the database every second. Most configurations do not need this many workers. Additionally, when using SQLite as the underlying database it is generally inadvisable to run more than one worker at a time, as SQLite does not have the .
85
85
86
86
The polling interval can be changed using the `refreshInterval` configuration setting:
Copy file name to clipboardExpand all lines: Sources/QueuesFluentDriver/Documentation.docc/Documentation.md
+35-3Lines changed: 35 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,22 @@ A driver for [Queues]. Uses [Fluent] to store job metadata in an SQL database.
9
9
[Queues]: https://github.com/vapor/queues
10
10
[Fluent]: https://github.com/vapor/fluent
11
11
12
-
## Overview
12
+
## Compatibility
13
+
14
+
This package makes use of the `SKIP LOCKED` feature supported by some of the major database engines (most notably [PostgresSQL][postgres-skip-locked] and [MySQL][mysql-skip-locked]) when available to make a best-effort guarantee that a task or job won't be picked by multiple workers.
15
+
16
+
This package should be compatible with any SQL database supported by the various Fluent drivers. It is specifically known to work with:
17
+
18
+
- PostgreSQL 11.0+
19
+
- MySQL 5.7+
20
+
- MariaDB 10.5+
21
+
- SQLite
22
+
23
+
> [!WARNING]
24
+
> Although SQLite can be used with this package, SQLite has no support for advanced locking. It is not likely to function correctly with more than one or two queue workers.
By default, the Vapor Queues system starts 2 workers per available CPU core, with each worker would polling the database once per second. On a 4-core system, this would results in 8 workers querying the database every second. Most configurations do not need this many workers.
91
+
By default, the Vapor Queues system starts 2 workers per available CPU core, with each worker would polling the database once per second. On a 4-core system, this would results in 8 workers querying the database every second. Most configurations do not need this many workers. Additionally, when using SQLite as the underlying database it is generally inadvisable to run more than one worker at a time, as SQLite does not have the necessary support for cross-connection locking.
60
92
61
93
The polling interval can be changed using the `refreshInterval` configuration setting:
0 commit comments