lekker

3 ms·

1.
by lekker 9y ago
They are a little verbose, though it is likely not to cause problems here. I suppose that it may slow things down a very tiny bit. The author could possibly have been trying to future-proof it with a bit more verbosity in the face of allowi
2.
by lekker 10y ago
GPU hardware on Amazon is quite pricey. I would be careful since it can get out of hand rather quickly.
3.
by lekker 10y ago
Oh, that looks really interesting. I'll definitely give this a bash
4.
by lekker 10y ago
It had 512MB of RAM, which I realise is a bit rediculous to run anything like this. I don't have a whole lot of budget for R&D so I try to keep things cheaper where possible.
5.
by lekker 10y ago
All right, thank you. I'll look into the other options you mentioned
6.
by lekker 10y ago
Currently we have a Postgres database and run manual queries against it. One-off hackjob turned production.
7.
by lekker 10y ago
Okay, thank you. I've been looking into Rabbit quite a bit. I like the stream processing aspect of Kafka, where you can introspectively peek into things as they happen rather than a straight message queue. Some of our stuff is on the G
8.
by lekker 10y ago
All right, that makes sense. It is likely that we'll see a peak in the 10s of thousands at a time, if that. Probably more as we move into the future. I want to avoid deploying a piece of software now that we'll need to swap out in
9.
by lekker 10y ago
I've been eyeing Kafka for a long time now - tried to set it up on a smaller DO box and had memory issues. Is it worth using this for smaller operations (<100k requests per day)? The stream processing seems extremely useful for my u