ukd1

26 ms·

301.
by ukd1 7y ago
An array can be appropriate for queuing for some things. You're wrong - as you are trying to state "a problem" has a specific solution, yet you don't know the problem. Yes, there are situations when using a dedicated mes
302.
by ukd1 7y ago
Is there any proof they hold $75mm in BTC? I didn't see any on the site. Why; I could have put this page up.
303.
by ukd1 7y ago
I mean, I love testing, but this is a great example of why you should just use less things if you can. Combinations of failure modes aren't fun to get right.
304.
by ukd1 7y ago
So much love for this; 'Every piece of complexity you incur should be proven as required', plus 'Fewer pieces in the technology stack is better, because each piece is operationally expensive'. Also, this totally ignores
305.
by ukd1 7y ago
It's not bad-engineering at all; how many engineers have to operate at that level in your stack, ever. Close to zero, as normally they just use an abstraction on top of it - Rails for instance is ActiveJob. No one has to care what&#x27
306.
by ukd1 7y ago
Some of these systems also check if the worker running the job is still alive, then if it's not kill the transaction. The job then restarts. Also, you can do this by time - when did it lock it, how long does it have to complete before
307.
by ukd1 7y ago
UNLOGGED: You could, but if you get some types of crash, you'd be in trouble. More on non-durable settings here - https://www.postgresql.org/docs/current/non-durability.html
308.
by ukd1 7y ago
Maybe chanks recalls differently; but I think the backstory was he saw / was interested in this - but wanted to use newer features that came out in Postgres. QueueClassic's first release was early 2011; it wasn't fast support
309.
by ukd1 7y ago
Ya, it doesn't mean streams - even if it's consistent in isolation, you're using it with Postgres - how do you make actions in one consistent with actions in the other? (TLDR: you won't/don't)
310.
by ukd1 7y ago
You can disagree, but you're still at least partially wrong; if you're using postgres already, adding redis WILL make your system less reliable as you now have another point of failure to deal with (something else to patch, keep u
311.
by ukd1 7y ago
We did; but I think it came around after we started. It was faster at that time, we looked at also it's well written - we'd probably have used it if it was out, but we didn't really mind about the speed - we're not laten
312.
by ukd1 7y ago
I think the biggest bonus for me of transactional queues like this is knowing that either everything worked - the inserted/updated/deleted things, and enqueuing of any jobs - or nothing did. Whilst using resque, or anything else o
313.
by ukd1 7y ago
https://www.2ndquadrant.com/en/blog/what-is-select-skip-lock... - is actually a pretty good post explaining the before (aka this gist) and after (aka skip locked). Another way of doing it was (now pointless) using
314.
by ukd1 7y ago
This post is pretty out of date; Que and QueueClassic moved to SKIP LOCKED at some point, over using advisory locks / lock head methods. It's much faster, but only supported in Postgres >= 9.5.
315.
by ukd1 7y ago
There is also QueueClassic ( https://github.com/QueueClassic/queue_classic); another Ruby based project. Recently I benchmarked some improvements we made to it vs Que (before and after) - it's now faster which is k
316.
by ukd1 7y ago
yep, but you'd still not get much useful if each one is maxed out - maybe a little more?
317.
by ukd1 7y ago
It's actually pretty easy; I compile stuff on a mac, then run it on a Linux box regularly. Usually use Docker though.
318.
by ukd1 7y ago
The Bridgify ToS are egregious; under "Messaging Content", you grant them irrevocable rights to use your messaging content...
319.
by ukd1 7y ago
You can brake-boost, which negates most of the lag in a turbo'd car. Still not as flat curve, but reduces / kills the lag.
320.
by ukd1 7y ago
It might be higher quality, but the paywall sucks.
321.
by ukd1 7y ago
Ya; that's another one - the same wallet on multiple machines = different set of contracts. Didn't notice that was fixed though...
322.
by ukd1 7y ago
Long time user and follower of Sia. It's always surprising to me that it's overlooked compared to filecoin (which is similar, but seems like $250m+ vaporware to date). I use it to have tertiary backups. Weird caveat I found: the s
323.
by ukd1 7y ago
It's kinda designed to expect that; you end up paying for more redundancy over more hosts, which is a win. Yes some will / may be down, but a) they're penalized financially, b) you can (by default do) have redundancy
324.
by ukd1 7y ago
Ah, it works on Catalina. I don't use Safari.
325.
by ukd1 7y ago
Seems to work fine, I installed Bitwarden yesterday
326.
by ukd1 7y ago
The point is all that stuff (jenkins, k8s, ansible) is accidental complexity that, I presume someone at your company has-to/had-to think about. I think Dark's angle is it's stuff you shouldn't need to think about in orde
327.
by ukd1 7y ago
CORS isn't supported to localhost, aka you can't do that; hence the image-size hack
328.
by ukd1 7y ago
Why? IMHO, and from on-boarding a bunch of folks for my startup, it's because it makes teaching you the software easier and more personal. If you aren't comfortable doing it, that's fine; but I believe it's designed to m
329.
by ukd1 7y ago
^ this
330.
by ukd1 7y ago
Or you could just use siacoin, which already does this for storage

More ›