motorest

8 ms·

91.
by motorest 1y ago
> While that's true, there is some market clearing price in which the activity just ceases to exist. The article cites a mechanic commenting on Ford CEO's remarks on lack of mechanics by referring to how Ford fails to pay rates
92.
by motorest 1y ago
> It's not clear to me what the difference is between what you're saying and what the parent comment says. The key difference is whether rentism plays a role or not. It's one thing to claim that no one will pay a mechanic
93.
by motorest 1y ago
> Still odd. The OS should be able to manage the memory and balance performance more efficiently than that. There’s no reason to preallocate memory by hardware. You are arguing hypotheticals, whereas for decades the world had to deal wit
94.
by motorest 1y ago
> Why do we need commercial ram drive apps when Linux has tmpfs, or is this a historical thing? A) this technique precedes the existence of Linux. B) Linux is far from the most popular OS in use today. C) some software development projec
95.
by motorest 1y ago
> . If you need to justify your lack of "something" ("It's not a hack because..." or "I don't use OOP because..." or "I duplicated this code because..."), then it feels like it says somet
96.
Health Check Response Format for HTTP APIs(datatracker.ietf.org)
2 points by motorest 1y ago|0 comments
97.
by motorest 1y ago
> If you can make many replicators, money stops making much sense. You probably end up with energy (if these devices take a lot of energy to operate) as the new currency. If you can make many replicators, you certainly won't be prov
98.
by motorest 1y ago
> I'm interested in... why? What are you building that loading data from disk is so lopsided vs CPu load from compiling (...) This has been the basic pattern for ages, particularly with large C++ projects. C++ builds, specially with
99.
by motorest 1y ago
> I'm not sure that your objection puts anything to rest, least of all a "cargo cult mentality". You re-assert exactly what I say just to disagree and miss the rest of the post. Not quite. I'm pointing out how your ar
100.
by motorest 1y ago
> This changes how you build your program on a fundamental level. I think this manifestation of cargo cult mentality should be put to rest. For each paradigm we heard the same story, but we still see programs in ${LANGUAGE_A} not even fo
101.
by motorest 1y ago
> Similar to how relational databases and SQL are still the gold standard today. ...except they aren't. The world is gradually slipping towards nosql databases and stepping away from normalized data stores, to the point where tried
102.
JavaScript: Designing a Language in 10 Days (2012)(computer.org)
1 points by motorest 1y ago|1 comments
103.
Software Optimization Resources(agner.org)
3 points by motorest 1y ago|0 comments
104.
by motorest 1y ago
> DoS is a performance problem Not really. Running out of computational resources to fulfill requests is not a performance issue. Think of thinks such as exhausting a connection pool. More often than not, some components of a system can&
105.
by motorest 1y ago
> what are these "extraordinary claims" you speak of? The claim that using postgres to store data, such as a cache, "is a bit concerning in terms of reliability".
106.
by motorest 1y ago
> It's $9/mo for 100 MB of ElastiCache Serverless which is HA. You need to be more specific with your scenario. Having to cache 100MB of anything is hardly a scenario that involves introducing a memory cache service such as Red
107.
by motorest 1y ago
> At 10k RPS you'll see a significant cost savings with Redis over DynamoDB. You need to be more specific than that. Depending on your read/write patterns and how much memory you need to allocate to Redis, back of the napkin ca
108.
by motorest 1y ago
> No need to be so combative. You're confusing being "combative" with asking you to substantiate your extraordinary claims. You opted to make some outlandish and very broad sweeping statements, and when asked to provide an
109.
by motorest 1y ago
> "I'll use postgres" was going to be your conclusion no matter what I guess? Would it bother you as well if the conclusion was rephrased as "based on my observations, I see no point in rearchitecting the system to im
110.
by motorest 1y ago
> The main issue is that a reader might mistake Redis as a 2X faster postgres. Memory is 1000X faster than disk (SSD) and with network overhead Redis can still be 100X as fast as postgres for caching workloads. Your comments suggest that
111.
by motorest 1y ago
> But when PG is running out of open connections or has already consumed all available CPU even the simplest query will struggle. I don't think it is reasonable to assume or even believe that connection exhaustion is an issue specif
112.
by motorest 1y ago
> But using it as a cache is a bit concerning in terms of reliability, in my opinion. This was the very first time I heard anyone even suggest that storing data in Postgres was a concern in terms of reliability, and I doubt you are the o
113.
by motorest 1y ago
> "If we don't need performance, we don't need caches" feels like a great broader takeaway here. I don't think this holds true. Caches are used for reasons other than performance. For example, caches are used in
114.
by motorest 1y ago
> High read/write and low-ish size. Also it's faster You posted a vague and meaningless assertion. If you do not have latency numbers and cost differences, you have absolutely nothing to show for, and you failed to provide any
115.
by motorest 1y ago
> At certain scales Redis is cheaper. Can you specify in which scenario you think Redis is cheaper than caching things in, say, dynamodb.
116.
by motorest 1y ago
> A TTL doesn't really tell you if it's stale though (...) Non-sequitur,and imaterial to the discussion. > You should probably evict it when the write comes in. No. This is only required if memory is maxed out and there is n
117.
by motorest 1y ago
> I've done this many times in AWS leveraging dynamodb. Exactly. I think nosql offerings from any cloud provider already supports both TTL and conditional requests out-of-the-box, and the performance of basic key-value CRUD operatio
118.
by motorest 1y ago
Why are you confusing memory capacity as a requirement to store the whole database in memory? I mean, think. What do you think is the biggest performance bottleneck with caches, and how does this relate to memory capacity?
119.
by motorest 1y ago
> If we don't use a TTL, aren't we going to have to either accept that our cache will grow without bounds (...) Do you have a bound? I mean, with Redis you do, but that's primarily a cost-driven bound. Nevertheless, I thin
120.
by motorest 1y ago
> Why would you cache the entire database though? I have no ideas where did you got that from.

More ›