Kully3xf_

Activity Graph

Page 1 of 1

2015-07-31

[19:30:58] Kully3xf_: has joined #ruby
[19:53:32] Kully3xf_: Ping timeout: 256 seconds

2015-07-30

[15:29:13] Kully3xf_: has joined #ruby
[15:43:45] Kully3xf_: Ping timeout: 246 seconds

2015-07-29

[12:42:06] Kully3xf_: has joined #ruby
[13:38:13] Kully3xf_: Ping timeout: 255 seconds
[13:55:29] Kully3xf_: has joined #ruby
[14:24:32] Kully3xf_: Remote host closed the connection

2015-07-27

[16:57:44] Kully3xf_: has joined #ruby
[18:09:05] Kully3xf_: Ping timeout: 250 seconds

2015-07-22

[14:08:44] Kully3xf_: has joined #ruby
[15:59:13] Kully3xf_: Ping timeout: 264 seconds

2015-07-21

[13:10:32] Kully3xf_: has joined #ruby
[13:21:33] Kully3xf_: Ping timeout: 250 seconds
[13:31:59] Kully3xf_: has joined #ruby
[14:24:36] Kully3xf_: Ping timeout: 246 seconds
[14:25:45] Kully3xf_: has joined #ruby
[15:09:54] Kully3xf_: *.net *.split
[15:50:55] Kully3xf_: has joined #ruby
[17:14:40] Kully3xf_: Ping timeout: 255 seconds
[20:56:08] Kully3xf_: has joined #ruby
[21:00:28] Kully3xf_: Ping timeout: 252 seconds

2015-07-20

[18:04:06] Kully3xf_: has joined #ruby
[21:43:11] Kully3xf_: Ping timeout: 248 seconds

2015-07-17

[12:39:51] Kully3xf_: has joined #ruby
[12:40:34] Kully3xf_: Remote host closed the connection
[12:48:42] Kully3xf_: has joined #ruby
[12:50:16] Kully3xf_: Remote host closed the connection
[17:38:33] Kully3xf_: has joined #ruby
[18:01:25] Kully3xf_: Remote host closed the connection

2015-07-16

[00:17:38] Kully3xf_: Read error: Connection reset by peer

2015-07-15

[12:47:00] Kully3xf_: has joined #ruby
[14:10:10] Kully3xf_: Ping timeout: 255 seconds
[14:58:18] Kully3xf_: has joined #ruby
[15:14:04] Kully3xf_: Ping timeout: 255 seconds
[16:31:29] Kully3xf_: has joined #ruby
[16:38:13] Kully3xf_: Ping timeout: 255 seconds
[22:50:39] Kully3xf_: has joined #ruby

2015-07-14

[13:57:14] Kully3xf_: has joined #ruby
[14:01:48] Kully3xf_: Ping timeout: 264 seconds
[17:27:02] Kully3xf_: has joined #ruby
[17:46:18] Kully3xf_: Ping timeout: 240 seconds
[19:52:57] Kully3xf_: has joined #ruby
[19:54:14] Kully3xf_: Remote host closed the connection

2015-07-13

[13:44:11] Kully3xf_: has joined #ruby
[13:48:18] Kully3xf_: Ping timeout: 240 seconds

2015-07-10

[18:07:23] Kully3xf_: has joined #ruby
[18:58:44] Kully3xf_: Ping timeout: 252 seconds
[19:20:34] Kully3xf_: has joined #ruby
[19:39:07] Kully3xf_: Ping timeout: 244 seconds

2015-07-08

[14:34:35] Kully3xf_: has joined #ruby
[15:14:10] Kully3xf_: Ping timeout: 252 seconds
[20:48:28] Kully3xf_: has joined #ruby
[21:29:13] Kully3xf_: Ping timeout: 264 seconds

2015-07-02

[14:04:18] Kully3xf_: has joined #ruby
[14:07:30] Kully3xf_: can someone explain these variable types real quick - :hn => 'hostname'
[14:07:36] Kully3xf_: what kind of variable is that
[14:08:12] Kully3xf_: why would I use that instead of a variable
[14:31:34] Kully3xf_: Ping timeout: 276 seconds
[18:16:46] Kully3xf_: has joined #ruby
[18:26:52] Kully3xf_: Ping timeout: 276 seconds

2015-07-01

[15:26:40] Kully3xf_: has joined #ruby
[15:27:17] Kully3xf_: Remote host closed the connection
[15:27:29] Kully3xf_: has joined #ruby
[15:29:09] Kully3xf_: thanks for the help on my last problem, now I have a question I'm not sure if it's possible, but each one of the jobs I'm spawing in the loop takes 30+ minutes, if I have to do 40 of them that's too long
[15:29:24] Kully3xf_: how can I make it so instead of a loop, it spawns them all as individual jobs
[17:04:13] Kully3xf_: what is a subcommand
[17:04:31] Kully3xf_: if I run something in a loop or by it self it works/but when I run it as threads it fails because it cannot find hte subcommand
[17:06:32] Kully3xf_: yea I think you're right
[17:06:36] Kully3xf_: I think it's a chef thing
[17:11:22] Kully3xf_: Ping timeout: 256 seconds
[17:14:28] Kully3xf_: has joined #ruby
[17:46:59] Kully3xf_: Ping timeout: 250 seconds
[17:50:10] Kully3xf_: has joined #ruby
[19:22:33] Kully3xf_: @miah thanks but I figured it out
[19:24:31] Kully3xf_: how many threads is too many threads
[19:24:44] Kully3xf_: I know it's subjective - but there has to be a rule of thumb?
[19:25:41] Kully3xf_: yea I figured
[19:26:45] Kully3xf_: c3.4xl - 16vcpu and 30gb ram
[19:26:56] Kully3xf_: I think it can prbably handle more than 10 threads?
[19:28:11] Kully3xf_: shouldn't need to launch more than 100 concurrent threads so I'll up the limit to 100
[19:31:39] Kully3xf_: ah you mean it could handle an absorbanant amount of thread
[19:31:47] Kully3xf_: day 1 of ruby
[19:33:44] Kully3xf_: I'll have to read up on it
[19:35:25] Kully3xf_: yea that's hard - gets expensive. The work load it's doing is launching large size instances, so I can only test it occasionally
[19:47:40] Kully3xf_: it takes 35 minutes to spawn a node - in a loop that takes WAY to long if you do even 2 of them. Thus the threading, cuts times like crazy
[19:47:51] Kully3xf_: if I can thread 100 we can launch 100 in 35 minutes
[19:48:14] Kully3xf_: if I can thread only ten then I'm still looking at 6 hours
[19:48:24] Kully3xf_: much better than before though
[19:48:43] Kully3xf_: yea I'm not really sure what happens on the back end - I'll have to do some testing when I get the chance next
[19:48:52] Kully3xf_: it be really sweet if I could up that limit
[19:49:03] Kully3xf_: maybe I'll include it as an upgrade xD
[21:09:37] Kully3xf_: Ping timeout: 276 seconds