BBHoss

Activity Graph

Page 1 of 1

2019-08-22

[00:56:30] BBHoss: *.net *.split
[01:14:06] BBHoss: has joined #elixir-lang

2019-07-11

[21:39:51] BBHoss: I'm looking into creating a new library which will start a couple of processes. I'm reading the library guidelines and it's not exactly clear to me how I should avoid the antipatterns associated with this. Should I have a supervisor tree in my library that the user adds to their application supervisor manually, adding the various config parameters to use the library?
[21:41:02] BBHoss: Previously (like years ago), you just wired up whatever you needed in the library, then that library/application was started automatically when you used it in your app, or you manually added it to the list of applications. But that used configuration to config the library which is another antipattern, so I am thinking that can't be the right way to do things in 2019
[21:45:58] BBHoss: right, that's exactly what I was thinking. It's totally possible to have multiple with different options. Would I still do mix new foo_lib --sup though? I thought that generated an app with a main application supervisor that will get auto-started
[21:46:15] BBHoss: maybe I don't do that at all, and just provide code that returns a supervisor spec or something
[21:46:58] BBHoss: great, that makes sense. thanks
[22:07:03] BBHoss: benwilson512: do you know of a library that implements this pattern I can follow as a reference? Mainly for naming and stuff
[22:09:09] BBHoss: looks like maybe plug does this

2019-05-27

[19:17:20] BBHoss: Read error: Connection reset by peer
[19:40:26] BBHoss: has joined #elixir-lang

2019-05-02

[01:18:00] BBHoss: Ping timeout: 252 seconds
[01:55:32] BBHoss: has joined #elixir-lang

2019-04-16

[06:32:01] BBHoss: Ping timeout: 258 seconds
[06:46:15] BBHoss: has joined #elixir-lang
[06:48:03] BBHoss: Max SendQ exceeded
[06:52:16] BBHoss: has joined #elixir-lang

2019-04-13

[16:49:50] BBHoss: *.net *.split

2019-03-31

[03:54:15] BBHoss: Ping timeout: 252 seconds
[03:55:32] BBHoss: has joined #elixir-lang

2019-03-22

[04:32:25] BBHoss: Ping timeout: 250 seconds
[04:34:25] BBHoss: has joined #elixir-lang

2019-03-20

[18:31:32] BBHoss: Ping timeout: 252 seconds
[18:34:36] BBHoss: has joined #elixir-lang

2017-06-20

[00:17:14] BBHoss: *.net *.split
[00:22:40] BBHoss: has joined #RubyOnRails

2017-06-07

[21:29:24] BBHoss: Ping timeout: 240 seconds

2017-05-09

[02:25:05] BBHoss: has joined #RubyOnRails

2017-05-02

[14:42:57] BBHoss: Ping timeout: 264 seconds
[15:07:57] BBHoss: has joined #RubyOnRails

2016-07-10

[05:00:02] BBHoss: *.net *.split
[08:54:07] BBHoss: has joined #RubyOnRails

2016-06-09

[05:25:06] BBHoss: Ping timeout: 260 seconds
[05:36:33] BBHoss: has joined #RubyOnRails

2016-05-18

[08:45:43] BBHoss: Ping timeout: 250 seconds

2016-05-07

[22:04:37] BBHoss: Ping timeout: 250 seconds
[22:05:31] BBHoss: has joined #RubyOnRails

2016-04-27

[06:58:41] BBHoss: Ping timeout: 264 seconds
[07:03:18] BBHoss: has joined #RubyOnRails

2016-03-30

[18:05:09] BBHoss: Ping timeout: 244 seconds
[18:07:00] BBHoss: has joined #RubyOnRails

2016-03-23

[19:19:51] BBHoss: Ping timeout: 250 seconds

2016-03-17

[22:41:52] BBHoss: Ping timeout: 264 seconds
[22:43:51] BBHoss: has joined #RubyOnRails

2016-03-10

[08:36:15] BBHoss: Ping timeout: 250 seconds
[08:40:24] BBHoss: has joined #RubyOnRails

2016-02-22

[11:40:02] BBHoss: Ping timeout: 240 seconds
[11:42:34] BBHoss: has joined #RubyOnRails

2016-02-16

[23:38:43] BBHoss: *.net *.split

2016-02-02

[12:36:29] BBHoss: Ping timeout: 240 seconds
[12:38:46] BBHoss: has joined #RubyOnRails

2016-01-31

[23:20:15] BBHoss: Ping timeout: 240 seconds
[23:22:11] BBHoss: has joined #RubyOnRails

2016-01-30

[01:04:05] BBHoss: *.net *.split

2016-01-13

[18:18:37] BBHoss: has joined #RubyOnRails

2015-12-13

[10:28:27] BBHoss: Ping timeout: 260 seconds
[10:43:38] BBHoss: has joined #RubyOnRails

2015-12-02

[15:39:14] BBHoss: *.net *.split
[16:47:59] BBHoss: has joined #RubyOnRails
[19:33:32] BBHoss: Remote host closed the connection
[20:05:36] BBHoss: has joined #RubyOnRails

2015-12-01

[11:38:56] BBHoss: Ping timeout: 276 seconds
[11:41:44] BBHoss: has joined #RubyOnRails

2015-11-29

[21:11:19] BBHoss: *.net *.split
[21:24:46] BBHoss: has joined #RubyOnRails

2015-11-27

[11:01:23] BBHoss: Ping timeout: 264 seconds
[11:03:16] BBHoss: has joined #RubyOnRails

2015-11-26

[19:02:02] BBHoss: *.net *.split

2015-11-14

[05:51:04] BBHoss: Ping timeout: 250 seconds
[06:00:46] BBHoss: has joined #RubyOnRails

2015-11-04

[04:11:28] BBHoss: Ping timeout: 240 seconds

2015-10-30

[03:06:11] BBHoss: Read error: Connection reset by peer
[03:10:04] BBHoss: has joined #RubyOnRails

2015-10-21

[17:29:49] BBHoss: Ping timeout: 240 seconds
[17:31:02] BBHoss: has joined #RubyOnRails

2015-10-16

[00:15:54] BBHoss: has joined #RubyOnRails

2015-10-12

[21:21:48] BBHoss: Ping timeout: 264 seconds
[22:04:46] BBHoss: has joined #RubyOnRails

2015-10-11

[02:28:36] BBHoss: Ping timeout: 252 seconds
[03:21:31] BBHoss: has joined #RubyOnRails
[08:36:08] BBHoss: Remote host closed the connection
[08:42:17] BBHoss: has joined #RubyOnRails

2015-10-09

[09:35:40] BBHoss: Ping timeout: 256 seconds
[10:04:32] BBHoss: has joined #RubyOnRails

2015-09-22

[09:53:42] BBHoss: has joined #RubyOnRails

2015-08-02

[19:17:57] BBHoss: has joined #RubyOnRails

2015-07-30

[18:34:55] BBHoss: Ping timeout: 240 seconds

2015-07-29

[16:13:26] BBHoss: Write error: Connection reset by peer
[16:28:09] BBHoss: has joined #RubyOnRails

2015-07-23

[17:04:24] BBHoss: has joined #RubyOnRails

2015-07-17

[05:23:25] BBHoss: Ping timeout: 252 seconds

2015-07-06

[12:51:03] BBHoss: has joined #RubyOnRails

2015-07-03

[15:08:21] BBHoss: has joined #RubyOnRails

2015-06-22

[16:25:09] BBHoss: has joined #RubyOnRails

2015-06-20

[20:15:00] BBHoss: *.net *.split

2015-06-09

[03:06:09] BBHoss: Remote host closed the connection
[06:18:56] BBHoss: has joined #RubyOnRails

2015-06-05

[18:54:06] BBHoss: Remote host closed the connection
[20:39:51] BBHoss: has joined #RubyOnRails

2015-05-22

[23:23:47] BBHoss: Ping timeout: 265 seconds
[23:25:59] BBHoss: has joined #RubyOnRails

2015-05-20

[19:54:42] BBHoss: has joined #RubyOnRails

2015-01-20

[00:02:37] BBHoss: unicorn worker is the same as the worker
[00:02:44] BBHoss: master just manages and routes requests IIRC
[00:02:50] BBHoss: nginx sits in front
[00:03:09] BBHoss: just play with it and see for yourself by observing

2015-01-19

[23:50:29] BBHoss: ravster: you can't like that.
[23:50:47] BBHoss: you need a has_many :through to images because thats many to many relationship
[23:51:11] BBHoss: I would also caution the use of polymorphic/STI as well, it performs terribly
[23:51:17] BBHoss: and is buggy
[23:51:24] BBHoss: dont use habtm eithher
[23:52:00] BBHoss: http://blog.flatironschool.com/post/35346328762/why-you-dont-need-has-and-belongs-to-many
[23:52:16] BBHoss: omosoj: yes, there are usually 1 process per core
[23:52:40] BBHoss: ravster: yeah, one side should be one type and the other should be image
[23:52:52] BBHoss: don't use polymorphhs at all, setup join tables/models for each
[23:53:15] BBHoss: omosoj: for MRI-based apps. jruby can run with real threading so mulitple apps is unneeded
[23:53:44] BBHoss: passenger also manages automatically, and puma can thread too. but typical setup is running X unicorns
[23:54:04] BBHoss: ravster: no, that's what you have now
[23:54:26] BBHoss: you need Post => PostImages <= Image
[23:54:59] BBHoss: MRI doesn't do threading the same way as JRuby and thus will not have the same performance
[23:55:13] BBHoss: due to the GIL or whatever nickname they have for it now
[23:55:48] BBHoss: nah, that speeds it up!
[23:56:04] BBHoss: if you're using MRI you will need to use passenger or unicorn/puma with multiple processes most likely
[23:56:08] BBHoss: omosoj: c extensions
[23:56:12] BBHoss: they are working on that though
[23:56:46] BBHoss: and also, the pre-JITted speed is pretty poor so developing with jruby can be a PITA
[23:57:18] BBHoss: but it's the best game in town if you don't use c extensions and can either put up with the slowness in development, or use Cruby for dev
[23:58:46] BBHoss: with Jruby 9000 + truffle they are working on supporting c extensions by interpreting the C code and converting it into bytecode which is itself JITted, so JRuby with C extentions can actually beat the speed of CRuby with C extensions in many cases
[23:59:17] BBHoss: omosoj: the child instances run the entire time, they are not spun-up per request