mattrobenolt

19 ms·

91.
Rethinking Roles(blog.getsentry.com)
2 points by mattrobenolt 11y ago|0 comments
92.
by mattrobenolt 11y ago
> So right now when we have a need to send a stacktrace (error or panic) we use Raven-Go's NewStacktrace to create a stacktrace and attach it to the packet we send up. In the UI I see the exception with surrounding lines. Yeah, so r
93.
by mattrobenolt 11y ago
> I'm wondering what the reasoning is behind suggesting I upload source artifacts to you as part of a release. The blog post even specifically calls out Go, which is what the majority of our application is written in. So from my und
94.
Rethinking Sentry's Documentation(blog.getsentry.com)
5 points by mattrobenolt 11y ago|0 comments
95.
The best tool for the job, isn’t always(medium.com)
14 points by mattrobenolt 12y ago|2 comments
96.
by mattrobenolt 12y ago
Just our realtime system, and we run some asynchronous tasks with Go now, specifying to replace a few things that were done by Celery previously. See this shitty thing I wrote to bridge the gap: https://github.com/mattrobeno
97.
by mattrobenolt 12y ago
For me, it felt comfortable writing Go, considering I've been mostly writing Python for the past 8 years. So the transition was a lot more natural, compared to using Scala or Erlang or anything else. Again, this is my subjective opinio
98.
by mattrobenolt 12y ago
I assure you, I built this in a week. :)
99.
by mattrobenolt 12y ago
To be fair, there were some optimizations that were made as well. Everyone does that, right? :) But overall, specifically our realtime service is a hybrid of CPU intensive tasks + lots of network IO. gevent was handling the network io witho
100.
by mattrobenolt 12y ago
We're not using a framework. This is a tiny component and the rest of Disqus is still Django.
101.
by mattrobenolt 13y ago
Disqus ( http://disqus.com/ ) needs some people to help break computers. http://boards.greenhouse.io/disqus?t=58y0kn#.UpuMT2RDsoM Let me know if something doesn't stand out. We're looking specifical
102.
by mattrobenolt 13y ago
It obviously depends on the project, but for something like Disqus or anything else large in terms of size, I'd still go with Django. For some personal projects, I like to use werkzeug, but they usually are very small and don't do
103.
by mattrobenolt 13y ago
Template fragment caching is not a good thing. We don't do this anymore. If you have to cache your template fragments, I generally think you're doing something wrong. Gonna have a bad time.
104.
by mattrobenolt 13y ago
We run 40 processes on each with 16 cores and 24G of RAM.
105.
by mattrobenolt 13y ago
http://blog.disqus.com/post/51155103801/trying-out-this-go-t... This has replaced that. ;)
106.
by mattrobenolt 13y ago
Servers are much cheaper than humans. First of all, the amount of time that'd be required to rewrite things in said "higher performance" language with the hopes of getting some improvements would be very costly. It's not
107.
by mattrobenolt 13y ago
We run many more than 12 processes per server. That's how you can get around that. :) But that's frankly more of a Python architecture problem than Django. Django is compatible with coroutine libraries like gevent, just most of th
108.
by mattrobenolt 13y ago
FWIW, PostgreSQL is our primary data store. It works well. ;)
109.
by mattrobenolt 13y ago
Varnish caches dynamic requests.
110.
by mattrobenolt 13y ago
Obviously you can't cache everything . Hence why we still have 15k/s that are hitting out backends. There are lots of more complicated things we can do with ESI if we really wanted to get into it.
111.
by mattrobenolt 13y ago
Sure. Any CDN is better than no CDN. :)
112.
by mattrobenolt 13y ago
I think what I'd like to get across more is that a lot of our dynamic content can be "static" as well, without going the static files route. Being static for shorter periods of time is something that we can achieve with Varni
113.
by mattrobenolt 13y ago
CloudFront is slow. :) Check out Fastly.
114.
by mattrobenolt 13y ago
Yeah, but that's an older unmaintained version. Official is at https://github.com/lib/pq , and I already shaved my yak. :) https://github.com/lib/pq/pull/135
115.
by mattrobenolt 13y ago
Fastly is used for some of our traffic yes, but not all. Our main app is not behind Fastly FWIW.
116.
by mattrobenolt 13y ago
I also write Go probably just as much as Python anymore, and the biggest set backs I have in Go is the immaturity of the ecosystem. Almost any project I work on, I have to shave 10 yaks to get things working right. My most recent yak was fi
117.
by mattrobenolt 13y ago
Also, to touch on your point about cookies, we do a few tricks to working around them and make conscious decisions about stripping them. My talks explain that a bit and how we design our app to work around it.
118.
by mattrobenolt 13y ago
I appreciate the kind words. :) Of course profiling is important. Even with starting on a greenfield project of this scale, I don't think I'd choose Go (which I spend a lot of time writing). The ecosystems aren't as mature in
119.
by mattrobenolt 13y ago
We do a mix of both, but mostly the actual ORM methods.
120.
by mattrobenolt 13y ago
This is a very simplified example. We do something similar to avoid a stampede.

More ›