Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
anarazel
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
55 ms
·
601.
▲
by
anarazel
7y ago
Imo this is one of the reasons why content on the web has become so much shallow.
602.
▲
by
anarazel
7y ago
> charged with being unbiased in a secret, electronically controlled ballot. The Iowa Caucuses are neither secret (like absurdly not) nor electronic?
603.
▲
by
anarazel
7y ago
That's only true if you actually need to access more than a few elements at once. And if you never need to insert/delete to/from anywhere but the end.
604.
▲
by
anarazel
7y ago
Really depends on the domain. There's some things that are a lot easier to make scale up in a language with a great concurrent gc, because that makes writing some lock free data structures quite fundamentally easier (no complicated mem
605.
▲
by
anarazel
7y ago
> So it seems like 2MB shared buffers shaves a few seconds off our tests. Is 2MB in the range you were thinking of? Well, hard to say without knowing anything about your tests. I think the cases where I've seen it make a really big
606.
▲
by
anarazel
7y ago
Heh, that's a bit awkward... Anyway, went into some details about why they are bad.
607.
▲
by
anarazel
7y ago
> And lastly, #4 - If your counterparty plays hardball with you, give them a truly fair offer that addresses their needs. If they don't take a fair deal when offered, be prepared to walk away. I think this is easier said than done.
608.
▲
by
anarazel
7y ago
Depends on what you define as "do this". It's pretty common for pointer heavy datastructures to replace the pointers with a narrower offset, and then a single base pointer which the offsets are added/subtracted to. If th
609.
▲
by
anarazel
7y ago
It'd also make syscalls a bit more expensive...
610.
▲
by
anarazel
7y ago
Realistically the limit for 32bit apps isn't 4GB, but considerably lower. The OS mapping takes out like 1gb at least. Then you have shared libraries mapped in. You want space for aslr. Mmapping files. Etc. Leaving available memory asid
611.
▲
by
anarazel
7y ago
> Without prefetching, a MODERN processor will NOT "stall" on the load instruction. A modern processor will execute out-of-order, branch predict the next iteration (its an inner loop, so its probably always taken), and then eff
612.
▲
by
anarazel
7y ago
The suggestions pgtune makes are really bad. It sets max_wal_size way too low, max_parallel_workers_per_gather to ridiculously high values, shared_buffers way too low, the work_mem settings make no sense whatsoever.
613.
▲
by
anarazel
7y ago
One caveat: Disabling fsyncs can hide problematic access patterns. If you were to e.g. accidentally perform a large set of DML in one-row increments and forgot to do so in one transaction, you'd not see a huge penalty in your test envi
614.
▲
by
anarazel
7y ago
If you're truncating/dropping tables all the the time, it can actually be beneficial to set shared_buffers to a pretty small value. When dropping/truncating, postgres needs to scan the buffer cache to get rid of all entries b
615.
▲
by
anarazel
7y ago
> Imagine if you could do this for all programming? [from chapter 6] rr comes pretty close. https://rr-project.org/
616.
▲
by
anarazel
7y ago
I don't understand that logic - the complex piece might require tons of research, experimenting with different approaches, benchmarking etc, before getting to something committable. And the successful result might only be a small numbe
617.
▲
by
anarazel
7y ago
> I think we're talking the difference between $300/month on open desk space vs $1000/month on an office I'd be very surprised if that were the extent of the difference. Are these numbers based on any data, or guesses
618.
▲
by
anarazel
7y ago
I got confused for a second, thinking of https://en.wikipedia.org/wiki/Venona_project
619.
▲
by
anarazel
7y ago
> (And this process has several caveat's-one of which is that it can produce unusable dumps in some rare cases and isn't complete. users, triggers etc aren't dumped iirc.. could be wrong there) Triggers are dumped, users n
620.
▲
by
anarazel
7y ago
> That's possible, brand loyalty is a thing I think there's also a rational aspect for some groups. Developers and related groups probably have outsized influence over what the whole market chooses. I e.g. do plenty low level p
621.
▲
by
anarazel
7y ago
> My question is, if they are collecting $50 million per year, why are my fees still so damn high? Well, the CA DMV has like 70 offices across the state. Even if you just calculate the portion of the cost for processing driver license m
622.
▲
by
anarazel
7y ago
I have no knowledge specific to this case, but it's pretty common for military hardware to have future capability upgrades scheduled for many years out. Which will then also need to be tested. It seems to make sense to have people with
623.
▲
by
anarazel
7y ago
There's no 8k limit with triggers? Could you expect on what you mean by that? One of the motivating factors for not using triggers is that the implied overhead is very significant. By logging changes separately which triggers the write
624.
▲
by
anarazel
7y ago
> Pre-fetching may be interesting if the first SQL query using prefetched data picks a small set of data stored on a disk plate here, then another one stored far away (distant cylinder), then back, then again far away, and so on... On a
625.
▲
by
anarazel
7y ago
Postgres does not use O_DIRECT for data (contrasting to the write ahead log / journal, where it can in some configurations), neither when reading, nor when writing. So data will definitely pass through the kernel page cache. By default
626.
▲
by
anarazel
7y ago
I'm fairly sure I was accurate. What exactly are you referring to?
627.
▲
by
anarazel
7y ago
> . but I'd say the same thing about Postgres recommending against use of NOT IN, which is a common construct and more readable than an anti-join. The recommendation against that is due to the semantics defined in the standard. If t
628.
▲
by
anarazel
7y ago
Note that that only was an issue in cases the storage system itself was failing (i.e. IO errors were generated). In contrast to protection against power failures etc, which was/is working correctly.
629.
▲
by
anarazel
7y ago
> He's been a good steward of the FSF Howso? He's held back gcc development repeatedly. He regularly forbids the emacs developers and maintainers to use their own judgement. Glibc as well. Independent of the current issue, this
630.
▲
by
anarazel
7y ago
The rise of ISIS certainly suggests that basically just packing up from a military POV may have very significant unintended consequences...
More ›