| 00:01:17 | | FiTheArchiver quits [Read error: Connection reset by peer] |
| 02:50:35 | | lys joins |
| 03:04:36 | | razul27 quits [Ping timeout: 260 seconds] |
| 03:12:28 | | razul27 joins |
| 03:13:22 | | monoxane quits [Quit: Ping timeout (120 seconds)] |
| 03:14:00 | | monoxane (monoxane) joins |
| 04:00:22 | | thenes quits [Ping timeout: 276 seconds] |
| 04:01:51 | | thenes (thenes) joins |
| 04:06:26 | | tek_dmn quits [Ping timeout: 260 seconds] |
| 04:07:13 | | tek_dmn (tek_dmn) joins |
| 04:14:36 | | myself quits [Ping timeout: 260 seconds] |
| 04:14:47 | | thenes quits [Remote host closed the connection] |
| 04:15:08 | | thenes (thenes) joins |
| 07:03:42 | | sec^nd quits [Remote host closed the connection] |
| 07:04:01 | | sec^nd (second) joins |
| 11:00:03 | | Bleo18260072271962345 quits [Quit: The Lounge - https://thelounge.chat] |
| 11:02:51 | | Bleo18260072271962345 joins |
| 11:30:06 | | BornOn420 quits [Remote host closed the connection] |
| 11:38:00 | | FiTheArchiver joins |
| 12:47:56 | | DLoader quits [Ping timeout: 260 seconds] |
| 13:16:15 | | DLoader (DLoader) joins |
| 15:05:59 | | BornOn420 (BornOn420) joins |
| 15:21:56 | | @Sanqui quits [Ping timeout: 260 seconds] |
| 15:53:35 | | Sanqui joins |
| 15:53:37 | | Sanqui is now authenticated as Sanqui |
| 15:53:37 | | Sanqui quits [Changing host] |
| 15:53:37 | | Sanqui (Sanqui) joins |
| 15:53:37 | | @ChanServ sets mode: +o Sanqui |
| 17:12:42 | <FiTheArchiver> | hi guys, just wanted to ask what the recommended concurrency on docker is? i know the warrior app is 6 but just wanted to know if docker was any different. i've been using docker for this for a while and notice i get more connection errors through that |
| 17:25:43 | <TheTechRobo> | FiTheArchiver: It depends on the exact project. The maximum is 20 per container, but most projects won't benefit from that. |
| 17:28:20 | <FiTheArchiver> | yeah i have always put 20 but i'm realising this is probably why it keeps breaking |
| 19:44:28 | <BornOn420> | FiTheArchiver There's no difference in concurrency between docker and warrior |
| 19:44:56 | <BornOn420> | diff in docker/warrior is your local implementation, stability, overhead, etc |
| 19:45:00 | <@JAA> | The warrior VM and the warrior container have the same limit (6). |
| 19:45:05 | <@JAA> | The project containers have the higher limit. |
| 19:45:34 | <BornOn420> | ah yes |
| 19:46:07 | <BornOn420> | but concurrency is there to prevent overload from the servers. you're requesting the data from |
| 19:48:13 | <BornOn420> | setting everything to 20 from one IP will put you on some 'naughty lists' quickly as I found out the hard way |
| 20:23:38 | | sec^nd quits [Remote host closed the connection] |
| 20:24:07 | | sec^nd (second) joins |
| 20:59:46 | | NatTheCat quits [Quit: nya~] |
| 21:46:07 | | NatTheCat (NatTheCat) joins |
| 23:24:39 | | FiTheArchiver quits [Read error: Connection reset by peer] |
| 23:58:59 | | fuzzy80211 quits [Read error: Connection reset by peer] |
| 23:59:41 | | fuzzy8021 (fuzzy80211) joins |