sams99

10 ms·

61.
by sams99 10y ago
most likely that bug, been tracking it, but I think this goes beyond this specific issue. It makes docker a lot more robust when bugs like this pop up in future.
62.
by sams99 10y ago
This is a huge upgrade that is super welcome. Recently (on 1.9) we have seen quite a few cases where we had "zombie" containers, these are container that can no longer be started or stopped due to cgroup misconfiguration or someth
63.
by sams99 11y ago
The thing I find amazing about this is how soon this has happened. We all were expecting this to eventually happen but if you asked anyone who played go and was across the computer go scene when it would happen, say a year ago, they would s
64.
by sams99 11y ago
I have been doing remote from Sydney for the past 9 years. Not sure about sites or directories (maybe try Stack Exchange jobs) As sad as it is, I think it is significantly easier to find a US or Europe based company to work for from Sydney
65.
by sams99 11y ago
Side note on fancy favicon stuff ... be sure to check out: https://github.com/discourse/discourse/blob/master/app/contr... You want your favicon asset on the same domain serving the page otherwise t
66.
by sams99 11y ago
Thanks heaps Nate for the writeup! Some other resources on rack-mini-profiler are: https://samsaffron.com/archive/2013/03/19/flame-graphs-in-ru... https://samsaffron.com/archive/2012
67.
by sams99 11y ago
MiniProfiler was originally developed at StackExchange for production profiling. It gave admins a clear picture of what is going on, all the time, and transformed the way we reasoned about performance. rack-mini-profiler is a port, I use it
68.
by sams99 11y ago
nice! I initially stayed away from lua due so I could support earlier redises, but these days I would totally take that dependency on to simplify the code. regarding that implementation, one diff I am spotting is that I also have a concept
69.
by sams99 11y ago
This is super interesting, I have a very similar project that we use at Discourse https://github.com/SamSaffron/message_bus clearly being an NGINX module nchan is going to be a LOT faster That said there are few little
70.
by sams99 11y ago
This is the alternative: https://github.com/SamSaffron/message_bus/blob/master/lib/me... its significantly less risky, timeouts and raise caused huge amount of pain at scale when I experimented in m
71.
by sams99 11y ago
awesome tool, I HUGE help would be allowing us to diff snapshots to catch leaks, I can see something is leaking but can not exactly track down what it is.
72.
by sams99 11y ago
"by operating the largest daily newspaper" Cough, I lived in Israel for many years... the biggest daily papers are https://en.wikipedia.org/wiki/Yedioth_Ahronoth (centralist) https://en.wikipedia.o
73.
by sams99 11y ago
for example, my redis container (samsaffron/redis) is 20mb, the official(tm) redis container is based on ubuntu is 100mb
74.
by sams99 11y ago
Yes, Aman and Koichi work very closely, the main point of difference at the moment is the method cache patches, Koichi is working on getting something similar implemented in MRI
75.
by sams99 12y ago
Throwing away a project that is clearly working is depressing. can't Heroku/GitHub/37 signals or someone sponsor a week of dev time to automate a system that runs the suite on latest? It's just such a better outcome, nob
76.
by sams99 12y ago
The thing I find depressing and frustrating about this kind of discussion is the fatalism and non-constructiveness. I really wish it was: "I set up a server that runs ruby spec on ruby-head daily and automatically reports spec failures
77.
by sams99 12y ago
> What tools do you need? A better profiler, chrome flamechart is probably the best out there, it would be really nice to have the same for Firefox. Also allowing to operate in "count every call mode" and "sampling" (
78.
by sams99 12y ago
GitHub are running 2.1.2 GitHub edition Ruby so that is a non-issue for them. 2 -> 3 migration is VERY VERY hard. 3 -> 4 should be relatively easy in comparison.
79.
by sams99 12y ago
also worth noting that you can still de-elavate the process in the container, discourse web runs under the discourse user in the container.
80.
by sams99 13y ago
That sir, is a bug that should be reported on bugs.ruby-lang while true do "a" * (1024 ** 2) end it is to do with the dynamic malloc limit growing too much, should be fairly trivial to patch in the next 2.1 release
81.
by sams99 13y ago
This article enrages me. I totally agree with codinghorror that a blog without comments in not a blog, this is a prime example. No way to respond to the author without jumping through crazy hoops. As to the issue. 1. NEVER use unicorn oobgc
82.
by sams99 13y ago
The bug, is not a "bug" its a feature missing to allow running with passenger. It works fine with unicorn.
83.
by sams99 13y ago
My blog runs Discourse as the backend http://www.webpagetest.org/result/140320_55_XPN/ just sayin...
84.
by sams99 13y ago
"and part of it is the backend is really really really resource hungry." hmmm ... we are serving our topic pages in 83ms median in 6 hours I can count 4 times it took us a second to serve a topic page. This is across MANY sites. s
85.
by sams99 13y ago
see my slides: https://speakerdeck.com/samsaffron/why-ruby-2-dot-1-excites-... only perf related feature is: RUBY_GC_OLDOBJECT_LIMIT_FACTOR ... you can set it to 1.5 to heavily reduce RSS usage of 2.1
86.
by sams99 13y ago
FYI we are also working on a similar project see: http://samsaffron.com/archive/2013/12/11/call-to-action-long... and http://community.miniprofiler.com/t/is-ruby-fast-yet/197
87.
by sams99 13y ago
Some of us like to pre-divine a world devoid of bugs and silliness, others like to provide us with tooling to track stuff down
88.
by sams99 13y ago
Wait, what about stackprof rb-lineprof flamegraph rack-mini-profiler
89.
by sams99 13y ago
The examples here are running the same exact benchmark on multiple versions of Ruby, the only moving part in those graphs is Ruby. Similar benches can just change the versions of Rails. Just change the version of Discourse and so on.
90.
Call to Action: long running Ruby benchmark(samsaffron.com)
3 points by sams99 13y ago|2 comments

More ›