|
|
3fcba4d050
|
v0.54 Tweak trust levels
|
2024-08-27 08:21:12 +10:00 |
|
|
|
85e01956f9
|
v0.53 Set to 2 threads for PostgreSQL pool size issue and remonitor. Need to consider memory consumption aspects as well of this after OOM
|
2024-08-20 11:45:10 +10:00 |
|
|
|
5735b78dc7
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 22:41:46 +10:00 |
|
|
|
bcc7519d78
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 22:21:16 +10:00 |
|
|
|
6360e99a96
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 22:09:38 +10:00 |
|
|
|
90ee7854b8
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 22:04:37 +10:00 |
|
|
|
e312a4ed12
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 22:01:47 +10:00 |
|
|
|
af3c46e1cf
|
v0.52 Improve handling and look at how we can improve ActiveRecord config for PostgreSQL and avoid insufficient pool size
|
2024-08-19 21:33:37 +10:00 |
|
|
|
e37ba1c8a9
|
v0.51 Fix mysql bug
|
2024-08-19 20:15:35 +10:00 |
|
|
|
f00fa9d67d
|
v0.51 Fix mysql bug
|
2024-08-19 20:00:59 +10:00 |
|
|
|
78749e28fc
|
v0.51 Fix mysql bug
|
2024-08-19 18:50:48 +10:00 |
|
|
|
e9750621bc
|
Revert "v0.48.6 40-40-40"
This reverts commit 6b4b728751.
|
2024-08-19 18:45:05 +10:00 |
|
|
|
5ef554b4e1
|
v0.50 Work on MySQL brokenness
|
2024-08-19 18:37:05 +10:00 |
|
|
|
6b4b728751
|
v0.48.6 40-40-40
|
2024-08-19 13:42:03 +10:00 |
|
|
|
7fde0fa255
|
v0.48.6 40-40-40
|
2024-08-19 13:38:43 +10:00 |
|
|
|
915961cf51
|
v0.48.6 40-40-40
|
2024-08-19 13:33:32 +10:00 |
|
|
|
9d6e1a0b7c
|
v0.48.6 48-48-48, add handling for deleted-former user as OP poster
|
2024-08-19 13:26:37 +10:00 |
|
|
|
a10df09d09
|
v0.48.5 Batch size 1000, double councurrency numbers
|
2024-08-19 13:11:16 +10:00 |
|
|
|
c8203b0410
|
v0.48.5 Batch size 1000, double councurrency numbers
|
2024-08-19 12:53:23 +10:00 |
|
|
|
198401f9f3
|
v0.48.5 Batch size 1000, double councurrency numbers
|
2024-08-19 12:50:41 +10:00 |
|
|
|
fc62e223ab
|
v0.48.5 Batch size 1000, double councurrency numbers
|
2024-08-19 12:45:01 +10:00 |
|
|
|
d9ae43b78b
|
v0.48.5 Batch size 1000, double councurrency numbers
|
2024-08-19 12:35:51 +10:00 |
|
|
|
74d2ee7382
|
v0.48.4 Batch size 1000
|
2024-08-19 12:13:27 +10:00 |
|
|
|
e0fd933526
|
v0.48.3 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-19 12:04:50 +10:00 |
|
|
|
f3c91267af
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 20:27:36 +10:00 |
|
|
|
ad7a5f945c
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 20:10:07 +10:00 |
|
|
|
6cb21584f3
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 20:02:21 +10:00 |
|
|
|
87f2733dbd
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 19:36:56 +10:00 |
|
|
|
395b2e9c49
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 19:24:33 +10:00 |
|
|
|
1d442ece31
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 19:16:03 +10:00 |
|
|
|
b0f300bf8e
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 18:57:22 +10:00 |
|
|
|
96c2b27250
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 18:26:16 +10:00 |
|
|
|
08f62e4288
|
v0.48.1 Further attempts to address MariaDB challenges and make things as foolproof as possible.
|
2024-08-18 17:09:46 +10:00 |
|
|
|
702d90cd34
|
v0.48 More attempts to address MariaDB craziness
|
2024-08-18 16:36:18 +10:00 |
|
|
|
eb6ec24033
|
v0.47.1 Fix .id nil bug
|
2024-08-18 16:35:52 +10:00 |
|
|
|
8caa2027cb
|
v0.47.1 Fix .id nil bug
|
2024-08-18 16:16:01 +10:00 |
|
|
|
2d233fdb42
|
v0.47.1 Fix .id nil bug
|
2024-08-18 16:13:05 +10:00 |
|
|
|
3e608d599b
|
v0.47.1 Fix .id nil bug
|
2024-08-18 16:08:14 +10:00 |
|
|
|
468b8b725b
|
v0.47 Significant tweaks and workarounds to try to improve smooth operation.
|
2024-08-18 15:56:12 +10:00 |
|
|
|
ddf59a09a5
|
v0.46 Restore use of ConnectionPool, tweak threads, mysql pool size, timeout, add full stacktraces
|
2024-08-18 15:06:30 +10:00 |
|
|
|
18d81d3880
|
v0.45 SQLIte mutexes only wrap around updates now
|
2024-08-18 05:47:22 +10:00 |
|
|
|
f7db3e8991
|
v0.45 SQLIte mutexes only wrap around updates now
|
2024-08-18 05:30:38 +10:00 |
|
|
|
0372db9cc7
|
v0.45 SQLIte mutexes only wrap around updates now
|
2024-08-18 05:12:42 +10:00 |
|
|
|
90a2d2fa37
|
v0.44 Try removing connection_pool and starting MySQL within thread method and fix handle_post_attachment
|
2024-08-18 04:39:51 +10:00 |
|
|
|
798153c8fc
|
v0.43 Move to connection pooling for MySQL problem
|
2024-08-18 03:35:41 +10:00 |
|
|
|
698c1b0f26
|
v0.43 Move to connection pooling for MySQL problem
|
2024-08-18 03:12:07 +10:00 |
|
|
|
855a0a9e46
|
v0.43 Move to connection pooling for MySQL problem
|
2024-08-18 02:41:56 +10:00 |
|
|
|
416dc9c1e0
|
v0.42.1 Rewrite and simplication of concurrent-ruby support
|
2024-08-18 02:01:31 +10:00 |
|
|
|
7b3a9babcb
|
v0.42.1 Rewrite and simplication of concurrent-ruby support
|
2024-08-18 01:44:29 +10:00 |
|
|
|
23a65c5f5c
|
v0.42.1 Rewrite and simplication of concurrent-ruby support
|
2024-08-18 01:23:54 +10:00 |
|
