Sinjo

7 ms·

31.
by Sinjo 11y ago
Thanks! Glad you enjoyed it. The main thing that narrowed it down was thinking about the request path from the app server to Elasticsearch. That pointed us at the load balancers (we tried a request directly from app -> Elasticsearch in p
32.
In search of performance – how we shaved 200ms off every POST request(gocardless.com)
87 points by Sinjo 11y ago|15 comments
33.
by Sinjo 11y ago
That was a fabricated example, rather than something plucked from our codebase. It's the sort of query we avoid running on our production database. I agree with your approach though. Our data analysis runs elsewhere.
34.
by Sinjo 11y ago
You're right on the approach. One thing to be careful of is that there's no option to add a not-null constraint with the `NOT VALID` flag. That means it'll hold the AccessExclusive lock while it checks every row in the table
35.
by Sinjo 11y ago
We can't count on a user (either in the browser or using the API) waiting around that long. Even some of our own services time out more aggressively than that. Those situations can be smoothed over with retries, but we try pretty hard
36.
by Sinjo 11y ago
Spot on. We ran the migrations against production-sized data beforehand, and everything was fine. We did it again after the downtime, and got the same results. Most of our queries are fast (tens of milliseconds or lower), which is how we go
37.
Zero-downtime Postgres migrations – the hard parts(gocardless.com)
98 points by Sinjo 11y ago|16 comments
38.
by Sinjo 12y ago
allow_mult has been enabled by default since at least 2.0 - http://docs.basho.com/riak/latest/dev/using/conflict-resolut...
39.
Using strace to solve a problem which didn't exist(blog.sinjakli.co.uk)
2 points by Sinjo 12y ago|0 comments
40.
Keeping your Elasticsearch cluster in sync(gocardless.com)
3 points by Sinjo 12y ago|0 comments
41.
Show HN: Eclipse Run Helper – Better Run/Debug support from the keyboard(blog.sinjakli.co.uk)
4 points by Sinjo 14y ago|0 comments
42.
Git explained using goats and paddocks(blog.prelode.com)
2 points by Sinjo 15y ago|0 comments
43.
by Sinjo 16y ago
I wrote a little follow up to the article, covering some of the points mentioned here and on reddit. http://blog.sinjakli.co.uk/2011/02/15/email-address-validati...
44.
Email address validation: an addendum(blog.sinjakli.co.uk)
13 points by Sinjo 16y ago|1 comments
45.
by Sinjo 16y ago
Hmm, I know it's a bit of an esoteric language, but Java has a method called "hashCode()" which is common to all objects, and does indeed return an int value. That's points 2 and 3 covered, I'll leave it up to you whether or not you want to
46.
by Sinjo 16y ago
As a little addendum to this piece, I now realise that WordPress does exactly the kind of horrible validation I was talking about in the article, and apologise for it.