00:57:57 | | sec^nd quits [Remote host closed the connection] |
00:58:15 | | sec^nd (second) joins |
01:10:09 | | fluke quits [Ping timeout: 260 seconds] |
01:12:43 | | fluke joins |
01:25:46 | | kansei- (kansei) joins |
01:27:08 | | kansei quits [Ping timeout: 276 seconds] |
03:04:38 | | razul27 quits [Ping timeout: 276 seconds] |
03:17:22 | | razul27 joins |
03:17:54 | | pabs quits [Ping timeout: 260 seconds] |
04:05:56 | | PwnHoaX (PwnHoaX) joins |
05:03:03 | | sec^nd quits [Remote host closed the connection] |
05:03:13 | | sec^nd (second) joins |
05:38:37 | | Guest58 joins |
05:41:05 | | pabs (pabs) joins |
05:51:54 | | @hook54321 quits [Ping timeout: 615 seconds] |
05:51:54 | | mrfooooo quits [Read error: Connection reset by peer] |
05:52:18 | | mrfooooo joins |
05:53:47 | | hook54321 (hook54321) joins |
05:53:47 | | @ChanServ sets mode: +o hook54321 |
06:14:35 | | UwU_93bydbco451y joins |
06:38:05 | | UwU_93bydbco451y1 joins |
06:39:03 | | UwU_93bydbco451y quits [Read error: Connection reset by peer] |
06:39:03 | | UwU_93bydbco451y1 quits [Read error: Connection reset by peer] |
06:40:47 | | UwU_93bydbco451y joins |
08:12:08 | | archiveDrill joins |
08:52:39 | | Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…] |
09:20:48 | | Guest58 joins |
09:40:02 | | Dango3602 (Dango360) joins |
09:42:54 | | Dango360 quits [Ping timeout: 260 seconds] |
09:42:54 | | Dango3602 is now known as Dango360 |
09:44:08 | | Guest58 quits [Client Quit] |
09:50:29 | | beardicus quits [Ping timeout: 260 seconds] |
09:51:18 | | beardicus (beardicus) joins |
10:00:07 | | Guest58 joins |
10:34:41 | | MrMcNuggets (MrMcNuggets) joins |
11:00:01 | | Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat] |
11:02:54 | | Bleo182600722719623455222 joins |
11:42:08 | | Gideon joins |
11:58:49 | | tzt quits [Ping timeout: 260 seconds] |
12:20:58 | | tzt (tzt) joins |
12:27:53 | | UwU_93bydbco451y quits [Quit: Dats about it, see ya.] |
12:51:55 | | Gideon quits [Client Quit] |
13:13:39 | | Gideon joins |
13:17:06 | <Gideon> | Hello! If I understand it correctly, the concurrency limit of 6 is there for a reason, and you should not spawn multiple Warrior instances running the same project (on the same IP at least). Is this correct? Is it useful to start instances for multiple different projects? Is there any reason not to have an instance (with CONCURRENCY=6) for every |
13:17:06 | <Gideon> | project, assuming that my bandwidth can take it? |
13:26:00 | <anonymoususer852> | The concurrency limit of 6 only applies to webUI, you can spawn multiple Warrior instances on the same project. The webUI is also limited to one project running at a time. Running it from within the terminal does allow up to 20 concurrency per docker instances. |
13:27:02 | <anonymoususer852> | Running several instances on the same IP isn't really advised from what I can gather, it can lead to either your IP being banned or you receiving abuse notices. |
13:29:28 | <nyakase> | (Depends on the ISP though. I've never had issues running multiple projects.) |
13:31:29 | <nyakase> | Lots of concurrency on the same project is likely to attract unwanted attention from the site owner, I suspect this is why the Warrior caps at 6 (many new users would likely just set to max and let it rip.) |
13:32:57 | <nyakase> | *on the same project on the same IP |
13:36:12 | | PredatorIWD25 quits [Read error: Connection reset by peer] |
13:38:43 | <nyakase> | If you don't think you'll get in trouble with your ISP, running multiple projects is fine. I would generally advise against running multiple of the same project (this depends on how much load the site is getting and how they handle it). |
13:42:12 | <anonymoususer852> | The important note from URLs page on wiki, https://wiki.archiveteam.org/index.php/URLs generally applies to running projects at scale, as a precaution. While it is possible to go above and beyond the limitations imposed by webUI, it's also a caveat emptor that one incurs any losses from doing so. |
13:43:03 | <anonymoususer852> | That is, if you do decided to run it at scale, do bewarned that there are potential consequences and that AT isn't going to be held accountable for. |
13:49:35 | <Gideon> | Alright, thanks! I'll just let a few different projects run with 6 each. |
13:51:33 | <anonymoususer852> | That's how I do it on a personal level. The other thing to keep in mind are VM constraints if you are running it inside the VM with the default or stock configuration. |
13:59:52 | <Gideon> | I'm running them in Docker containers on my Debian server, so no issues there |
13:59:56 | | Gideon quits [Client Quit] |
14:06:57 | | PredatorIWD25 joins |
15:04:03 | | MrMcNuggets quits [Quit: WeeChat 4.3.2] |
15:08:28 | | nulldata-alt quits [Quit: Ping timeout (120 seconds)] |
15:09:26 | | nulldata-alt (nulldata) joins |
18:59:30 | | BornOn420 quits [Remote host closed the connection] |
19:00:11 | | BornOn420 (BornOn420) joins |
19:14:36 | | Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…] |
20:23:59 | | pseudorizer quits [Ping timeout: 260 seconds] |
20:24:10 | | pseudorizer (pseudorizer) joins |
22:03:08 | | Meli quits [Remote host closed the connection] |
23:21:16 | | Webuser810541 joins |
23:22:38 | | Webuser810541 quits [Client Quit] |
23:37:42 | | nepeat (nepeat) joins |
23:45:04 | | ScenarioPlanet quits [Quit: meow meowy meow] |
23:45:04 | | TheTechRobo quits [Quit: Leave message goes here] |
23:48:38 | | kansei- quits [Quit: ZNC 1.10.0 - https://znc.in] |
23:49:05 | | kansei (kansei) joins |
23:51:22 | | ScenarioPlanet (ScenarioPlanet) joins |
23:51:59 | | nepeat quits [Ping timeout: 276 seconds] |
23:52:19 | | nepeat (nepeat) joins |
23:53:40 | | TheTechRobo (TheTechRobo) joins |
23:56:57 | | kansei quits [Client Quit] |