[00:18] *** nertzy has joined #warrior [00:41] *** adinbied has quit IRC (Remote host closed the connection) [01:01] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [01:33] *** alex____ has quit IRC (Quit: ZZzzz) [02:25] *** Isanami has joined #warrior [02:27] is Warrior CPU intensive to run? [07:24] *** alex___ has joined #warrior [09:05] *** astrid has quit IRC (Ping timeout: 1212 seconds) [09:21] *** astrid has joined #warrior [09:21] *** swebb sets mode: +o astrid [10:03] *** astrid has quit IRC (Ping timeout: 1212 seconds) [10:05] *** astrid has joined #warrior [10:05] *** swebb sets mode: +o astrid [12:35] Isanami: the (unofficial) docker container uses 0.2-0.8% cpu on a xeon e5-2670 for me. So i wouldn't say so no. [17:04] *** adinbied has joined #warrior [18:01] *** TigerbotH has quit IRC (ZNC - http://znc.in) [18:16] *** TigerbotH has joined #warrior [19:15] *** alex____ has joined #warrior [19:17] *** alex___ has quit IRC (Read error: Operation timed out) [19:37] *** SmileyG has joined #warrior [19:37] *** Smiley has quit IRC (Read error: Operation timed out) [19:44] *** SmileyG has quit IRC (Ping timeout: 260 seconds) [19:49] *** Smiley has joined #warrior [19:58] thanks, I plan on running it on a spare VPS i have that's doing nothing [22:50] *** astrid has quit IRC (Read error: Operation timed out) [22:52] *** astrid has joined #warrior [22:52] *** swebb sets mode: +o astrid [23:36] *** nertzy has joined #warrior