03:51:03 | | DogsRNice_ joins |
03:55:07 | | DogsRNice quits [Ping timeout: 255 seconds] |
04:04:47 | | DogsRNice_ quits [Read error: Connection reset by peer] |
04:26:58 | | HP_Archivist quits [Quit: Leaving] |
05:13:18 | | dxrt_ is now known as dxrt |
05:13:19 | | dxrt is now authenticated as dxrt |
05:13:19 | | dxrt quits [Changing host] |
05:13:19 | | dxrt (dxrt) joins |
06:14:32 | <@JAA> | SPN timing is funny. Half the requests are done in between 6.0 and 6.5 seconds. The rest seems to vaguely cluster just above multiples of 6 seconds. I wonder why this is. |
06:14:55 | <@JAA> | Something checking every 6 seconds whether the retrieval is done yet? |
06:15:39 | <@JAA> | (This is /save/URL.) |
06:23:19 | | Arcorann (Arcorann) joins |
07:11:34 | <@JAA> | I'm also in 6+ s/MiB upload town now. |
09:51:31 | | Ryz quits [Ping timeout: 255 seconds] |
09:54:29 | | Ryz (Ryz) joins |
11:08:26 | | SootBector quits [Remote host closed the connection] |
11:10:54 | | SootBector (SootBector) joins |
12:41:12 | | BearFortress quits [Client Quit] |
12:53:58 | | HP_Archivist (HP_Archivist) joins |
12:56:57 | | BearFortress joins |
13:01:47 | | PredatorIWD quits [Read error: Connection reset by peer] |
13:02:09 | | Arcorann quits [Ping timeout: 272 seconds] |
13:13:33 | <nicolas17> | https://catalogd.archive.org/history/samsung-opensource-11393 has been waiting to run for 17 hours now, huh |
13:29:35 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
13:30:19 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
14:11:39 | | qwertyasdfuiopghjkl quits [Client Quit] |
14:24:14 | | line_ joins |
14:25:07 | | line quits [Ping timeout: 272 seconds] |
14:26:21 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
15:57:06 | <@JAA> | Yeah, looks like derives have been piling up since approximately 2024-03-12 07:00 UTC. |
15:58:38 | <nicolas17> | JAA: if I accumulate too many pending tasks, will I get throttled? |
15:58:56 | <nicolas17> | afaik uploads start to fail if IA hits a global limit of pending tasks, but I don't know if there's a per-user limit too |
16:00:41 | <@JAA> | I hit a per-user limit before I think, but not in a good while, so not sure whether that's still a thing. |
16:01:48 | <nicolas17> | I'm at 40 tasks waiting to run, I guess that's long before hitting a wall |
16:02:48 | | DogsRNice joins |
16:06:22 | <@JAA> | I think I ran into a wall at 50 or 100 before, but that may also all have been on the same item. |
16:11:18 | <nicolas17> | I don't think I can upload fast enough to reach 100 ._. |
16:11:28 | <nicolas17> | but if tasks keep piling up, maybe |
16:12:18 | <nicolas17> | I don't mind if these tasks take long, I would give them lower priority in the queue if I could, but I do mind if that eventually prevents me from uploading |
16:13:27 | <Ryz> | So yeah...it looks like when using 'outlinks' function when doing WBM SPN, it only saves up to 40 outlinks, not 60 or 100, at least constantly :c |
16:14:49 | <@JAA> | You can assign a lower priority in theory, but not for auto-queued derives. |
16:15:26 | <@JAA> | And I'm not even sure the CLI exposes it at all. |
16:15:37 | <nicolas17> | I saw in the API that there's a way to assign *higher* priority (for "interactive uploads"? maybe the web UI does that?) |
16:38:07 | | PredatorIWD joins |
16:52:45 | | SootBector quits [Remote host closed the connection] |
16:58:20 | | SootBector (SootBector) joins |
18:13:10 | | qwertyasdfuiopghjkl quits [Client Quit] |
18:16:18 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
18:52:08 | | @AlsoJAA quits [Quit: Reconnecting] |
18:52:13 | | AlsoJAA (JAA) joins |
18:52:13 | | @ChanServ sets mode: +o AlsoJAA |
19:12:39 | | nicolas17 quits [Ping timeout: 272 seconds] |
22:00:07 | | nicolas17 joins |
22:04:50 | <Vokun> | nicolas17: I forgot to zip a folder once. It had several thousand sub 2kb files. I think it went well above 100 pending items before hitting any sort of limit |
22:05:16 | <Vokun> | though maybe file size is calculated in that limit as well. I remember it went above several hundred |
23:34:44 | <TheTechRobo> | I think I ran into an upload rate limit last year when uploading all the #burnthetwitch items (before it was automated). There was some reason I knew it was per-user, but I don't know what it was and cant confirm it. |
23:34:52 | <TheTechRobo> | Or maybe it was per-item. |
23:34:57 | <TheTechRobo> | The item had something like 750 pending tasks. |