| Time |
Nickname |
Message |
|
00:27
🔗
|
|
coderobe has quit IRC (Ping timeout: 252 seconds) |
|
00:29
🔗
|
|
tonsofpcs has quit IRC (Read error: Operation timed out) |
|
00:32
🔗
|
|
yawkat has quit IRC (Read error: Operation timed out) |
|
00:33
🔗
|
|
chazchaz_ has joined #warrior |
|
00:35
🔗
|
|
Decobus_ has joined #warrior |
|
00:35
🔗
|
|
Ryz has quit IRC (Read error: Connection reset by peer) |
|
00:35
🔗
|
|
yawkat has joined #warrior |
|
00:36
🔗
|
Wingy |
docker-compose up --scale warrior=4: 24 warrior threads! |
|
00:37
🔗
|
|
chazchaz has quit IRC (Read error: Operation timed out) |
|
00:37
🔗
|
Wingy |
My docker-compose: https://termbin.com/00rq |
|
00:38
🔗
|
|
Decobus has quit IRC (Ping timeout: 496 seconds) |
|
00:41
🔗
|
|
markedL has quit IRC (Ping timeout: 496 seconds) |
|
00:42
🔗
|
|
markedL has joined #warrior |
|
00:43
🔗
|
|
Ryz has joined #warrior |
|
00:44
🔗
|
|
nyany__ has joined #warrior |
|
00:44
🔗
|
|
nyany_ has quit IRC (Remote host closed the connection) |
|
00:45
🔗
|
|
markedL has quit IRC (Client Quit) |
|
00:45
🔗
|
|
tonsofpcs has joined #warrior |
|
01:13
🔗
|
Wingy |
Is warrior going to be cpu intensive? |
|
01:18
🔗
|
Wingy |
Wow I could run 6000 threads for $9/hour on Scaleway |
|
01:23
🔗
|
Datechnom |
Warrior is very lightweight |
|
01:24
🔗
|
Datechnom |
It typically only uses bandwidth and very minimal cpu and ram |
|
01:29
🔗
|
|
d5f4a3622 has quit IRC (Quit: https://i.imgur.com/xacQ09F.mp4) |
|
01:31
🔗
|
|
d5f4a3622 has joined #warrior |
|
01:44
🔗
|
|
Decobus_ has quit IRC (Read error: Connection reset by peer) |
|
01:45
🔗
|
|
Decobus has joined #warrior |
|
01:46
🔗
|
|
MrRadar2 has quit IRC (Read error: Connection reset by peer) |
|
01:50
🔗
|
|
coderobe has joined #warrior |
|
01:52
🔗
|
|
Dallas has quit IRC (Ping timeout: 864 seconds) |
|
01:53
🔗
|
|
Dallas has joined #warrior |
|
02:01
🔗
|
Wingy |
So is it okay to run like 48 threads when I have 12 cores? |
|
02:01
🔗
|
Wingy |
Datechnom? |
|
02:07
🔗
|
Datechnom |
That will run perfectly fine. I run the warrior client on docker with 3-4 instances per core |
|
02:07
🔗
|
Datechnom |
Each instance is 6 warrior threads |
|
02:07
🔗
|
Datechnom |
Wingy |
|
02:09
🔗
|
Kaz |
that *heavily* depends on which project you're running |
|
02:11
🔗
|
Wingy |
Ah okay thanks |
|
02:12
🔗
|
Wingy |
I'll run 1 instance per core I guess |
|
02:12
🔗
|
Kaz |
start slow, you can always scale up if usage is low |
|
02:13
🔗
|
Wingy |
It has been slow for urlteam |
|
02:16
🔗
|
Kaz |
urlteam is a special case, you're limited very hard per-ip there |
|
02:16
🔗
|
Wingy |
But it runs over different shorteners? |
|
02:16
🔗
|
Wingy |
It seems wasteful to spam the tracker though |
|
02:20
🔗
|
|
MrRadar2 has joined #warrior |
|
03:10
🔗
|
Datechnom |
Yeah no point having lots of warrior agents spamming the tracker when your limited by IP |
|
03:29
🔗
|
|
ShellyRol has quit IRC (Read error: Operation timed out) |
|
03:30
🔗
|
|
ShellyRol has joined #warrior |
|
03:38
🔗
|
|
Wingy has quit IRC (Read error: Operation timed out) |
|
04:24
🔗
|
|
markedL has joined #warrior |
|
08:08
🔗
|
|
d5f4a3622 has quit IRC (Ping timeout: 496 seconds) |
|
08:34
🔗
|
|
d5f4a3622 has joined #warrior |
|
11:28
🔗
|
|
d5f4a3622 has quit IRC (Ping timeout: 864 seconds) |
|
11:57
🔗
|
Zerote_ |
Datechom: sorry for the late reply, yes, the script uses the same websocket as the tracker, so if the tracker is down, the script will not work |
|
12:20
🔗
|
|
Wingy has joined #warrior |
|
13:40
🔗
|
Wingy |
Are there any active projects right now? |
|
13:40
🔗
|
Wingy |
urlteam is down |
|
13:41
🔗
|
Wingy |
angelfire has 0 tasks |
|
13:41
🔗
|
Wingy |
yourshot is ratelimited |
|
13:41
🔗
|
Wingy |
freeml is down |
|
13:42
🔗
|
Wingy |
sketch fails to install |
|
13:42
🔗
|
Wingy |
theartistunion has 0 tasks |
|
13:42
🔗
|
Wingy |
instaudio fails to install |
|
13:43
🔗
|
Wingy |
newsgrabber is down |
|
13:44
🔗
|
Wingy |
wikiteam has 0 tasks |
|
13:50
🔗
|
Wingy |
Shouldn’t Sketch be removed? |
|
14:20
🔗
|
tonsofpcs |
Wingy: urlteam is running here... |
|
14:21
🔗
|
tonsofpcs |
as is yourshot |
|
14:21
🔗
|
tonsofpcs |
as I understand it, yahoo should be up in a few days? |
|
14:21
🔗
|
Wingy |
Yeah |
|
14:21
🔗
|
Wingy |
So urlteam is back up? |
|
14:22
🔗
|
Wingy |
And yourshot is being heavily ratelimited. |
|
14:23
🔗
|
Wingy |
This is what I'm getting on urlteam: Error communicating with tracker: 500 Server Error: Internal Server Error for url: https://tracker.archiveteam.org:1338/api/done. |
|
14:25
🔗
|
tonsofpcs |
seems like it's intermittent? I've got one warrior getting that and two that don't appear to be. I've got one warrior running on yourshot, yes it's rate limited, but it's working. |
|
14:25
🔗
|
tonsofpcs |
oh, hmm, all three are now getting that.... they weren't when I just checked lol |
|
14:26
🔗
|
Wingy |
Maybe just run more warriors to get some that work? |
|
14:27
🔗
|
tonsofpcs |
eh, I just stopped two of them to stop hitting the tracker |
|
14:27
🔗
|
tonsofpcs |
if someone who knows the architecture and what's going on wants to tell me to run more or less or some specific number, please do :) |
|
14:41
🔗
|
Wingy |
I'll run 4 of urlteam and 2 of angelfire |
|
15:02
🔗
|
Zerote_ |
Angelfire is done, no? |
|
15:10
🔗
|
Wingy |
Oops I meant yourshot |
|
15:50
🔗
|
|
Zerote_ has quit IRC (Read error: Operation timed out) |
|
16:05
🔗
|
|
Zerote has joined #warrior |
|
16:36
🔗
|
|
ivan- has joined #warrior |
|
16:36
🔗
|
|
Fusl sets mode: +o ivan- |
|
16:36
🔗
|
|
Fusl_ sets mode: +o ivan- |
|
16:47
🔗
|
|
ivan has quit IRC (Ping timeout: 745 seconds) |
|
19:06
🔗
|
|
MaximeleG has joined #warrior |
|
19:47
🔗
|
|
d5f4a3622 has joined #warrior |
|
20:35
🔗
|
|
MaximeleG has quit IRC (Remote host closed the connection) |
|
20:38
🔗
|
JAA |
sketch, theartistunion, and instaudio are finished for a while. The wikiteam tracker project hasn't done anything in years. |
|
20:38
🔗
|
JAA |
But yeah, the only active projects at the moment are URLTeam and Your Shot. |
|
20:50
🔗
|
markedL |
yahoo groups, fusion tables, radio24, drawr, are in different states of almost |
|
20:51
🔗
|
JAA |
None of them are listed on the tracker anyway. |
|
20:56
🔗
|
Wingy |
yahoogroups is about to launch on 29th right? |
|
21:09
🔗
|
JAA |
I think so, but I haven't really followed the discussion in #yahoosucks. |
|
21:39
🔗
|
Zerote |
I see fusion tables referenced on the front page, but neither it nor radio24 have pages with more info, do they have irc channels or anything, if we want to follow the development? |
|
21:44
🔗
|
markedL |
radio24 is in #radioshmadio |
|
21:45
🔗
|
markedL |
fusion tables, the group with the most people lost ops, because nobody with a bot showed up |
|
21:48
🔗
|
Igloo |
drawr is written - But we're waiting till nearer the time too |
|
22:51
🔗
|
tonsofpcs |
JAA: should I run fewer instances with the tracker going in-and-out of screwy? or does it not matter and I should run my nominal 3 (urlteam)/1 (yourshot)? (or should I bump that up even higher?) |
|
22:57
🔗
|
|
ivan- is now known as ivan |
|
22:58
🔗
|
JAA |
tonsofpcs: At that scale, it doesn't matter. The tracker is getting murdered by people running thousands of pipelines, so a couple more don't make any difference. |
|
23:01
🔗
|
Igloo |
#sorrynotsorry |
|
23:02
🔗
|
markedL |
there's nobody in that channel |
|
23:03
🔗
|
tonsofpcs |
so I shouldn't make it less but I also shouldn't spin up a thousand more? :) |
|
23:04
🔗
|
JAA |
Yeah, basically. Talk to someone if you intend to spin up hundreds or more pipelines. |
|
23:04
🔗
|
|
JAA sets mode: +o Igloo |
|
23:10
🔗
|
tonsofpcs |
Well, four is using 2% of the allocated CPU and 20% of the allocated RAM of the VM... so I could probably spin up 1-200 if that'd be helpful... |
|
23:10
🔗
|
tonsofpcs |
not sure how much network traffic it's eating |
|
23:12
🔗
|
tonsofpcs |
(looks like it's peaking around 400k... so should be fine) |
|
23:16
🔗
|
JAA |
You won't get any benefits from that for URLTeam unless you also have a few dozen IPs. And Your Shot is heavily rate-limited because Nat Geo's servers suck. |
|
23:16
🔗
|
tonsofpcs |
right, so probably not useful to run more than the 4 I am? |
|
23:16
🔗
|
tonsofpcs |
and then we'll see how much yahoosucksextra later this week I guess |
|
23:18
🔗
|
JAA |
Yup |